OMG System Modeling Language Avatar
  1. OMG Specification

OMG System Modeling Language — Open Issues

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

Issues Summary

Key Issue Reported Fixed Disposition Status
SYSML2-453 Text error in List property construction SysML 2.0b1 open
SYSML2-454 PrefixComment should not be a production for AnnotatingElement SysML 2.0b1 open
SYSML2-452 misspelled ConjugatePortTyping should be ConjugatedPortTyping SysML 2.0b1 open
SYSML2-451 Missing production for ConjugatePortTyping SysML 2.0b1 open
SYSML2-431 Incorrect EBNF specification SysML 2.0b1 open
SYSML2-446 Document how SysML v1 properties are mapped to SysML v2 SysML 2.0b1 open
SYSML2-443 Property_Mapping should map to ItemUsage and the class name is misleading SysML 2.0b1 open
SYSML2-383 Decision/MergeNode SuccessionSpecialization checks missing some constraints SysML 2.0b1 open
SYSML2-450 Fork/JoinNode succession "other" end multiplicity validations missing SysML 2.0b1 open
SYSML2-418 Description of TimeEvent_Mapping is a note SysML 2.0b1 open
SYSML2-449 TimeEvent should be mapped to an accept action instead of TextualRepresentation SysML 2.0b1 open
SYSML2-416 Description of ChangeEvent_Mapping is a note SysML 2.0b1 open
SYSML2-448 ChangeEvent should be mapped to an accept action instead of TextualRepresentation SysML 2.0b1 open
SYSML2-425 LoopActionUsage descriptions refer to property not in metamodel SysML 2.0b1 open
SYSML2-424 WhileLoopsActionusage title typos SysML 2.0b1 open
SYSML2-423 checkIfActionUsageSpecialization OCL specifiesFromLibrary typo SysML 2.0b1 open
SYSML2-398 TransitionUsage effectAction attribute text and constraint are different SysML 2.0a1 open
SYSML2-414 checkTransitionUsageSourceBindingConnector text and OCL are different SysML 2.0b1 open
SYSML2-356 The OCL for the body of ConstraintUsage::namingFeature is incorrect SysML 2.0b1 open
SYSML2-303 validateStateDefinitionIsParallelGeneralization and validateStateUsageIsParallelGeneralization OCL is wrong SysML 2.0b1 open
SYSML2-306 validateStateDefinitionIsParallelGeneralization and validateStateUsageIsParallelGeneralization constraints are too restrictive SysML 2.0b1 open
SYSML2-302 validateOccurrenceUsageIndividualDefinition OCL is wrong SysML 2.0b1 open
SYSML2-301 validateUsageOwningType constraint is too restrictive SysML 2.0b1 open
SYSML2-299 validateDefinitionVariationSpecialization and validateUsageVariationSpecialization OCL is wrong SysML 2.0b1 open
SYSML2-300 validateDefinitionNonVariationMembership and validateUsageNonVariationMembership are redundant with validateVariantMembershipOwningNamespace SysML 2.0b1 open
SYSML2-298 validateDefinitionVariationMembership and validateUsageVariationMembership are too strict SysML 2.0b1 open
SYSML2-254 Redundant numbered list in language description of usage SysML 2.0a1 open
SYSML2-296 validateFramedConcernUsageConstraintKind constraint is misnamed SysML 2.0b1 open
SYSML2-253 Additional cases when usages are required to be referential SysML 2.0a1 open
SYSML2-218 Errors in TransitionUsage semantic constraints SysML 2.0a1 open
SYSML2-191 deriveForLoopActionUsageBodyAction is misnamed SysML 2.0a1 open
SYSML2-101 Time triggers are relative to "localClock", not "defaultClock" SysML 2.0a1 open
SYSML2-190 The description and derivation of ForLoopActionUsage::seqArgument is wrong SysML 2.0a1 open
SYSML2-99 Incorrect notation in action examples SysML 2.0a1 open
SYSML2-28 Validation constraints are missing in the SysML abstract syntax SysML 2.0a1 open
SYSML2-325 Wrong compartment name: documentation SysML 2.0b1 open
SYSML2-93 Keyword for documentation is "doc" SysML 2.0a1 open
SYSML2-439 UML4SysML::Class should be mapped to ItemDefinition 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-420 InformationFlow mapping classes should use GenericTo mapping classes SysML 2.0b1 open
SYSML2-412 SYSML2-180 uses non-existing general mapping class GenericToItemUsage_Mapping SysML 2.0b1 open
SYSML2-437 The transformation specification does not explicitly specify how to map a ValueType 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-445 ConstraintProperty should be mapped to a AssertConstraintUsage SysML 2.0b1 open
SYSML2-346 Incorrect notation in example "Binding Connection" SysML 2.0b1 open
SYSML2-430 Subsetting of subjectParameter properties is wrong SysML 2.0b1 open
SYSML2-426 specializesFromLibrary arguments use inconsistent notation for strings SysML 2.0b1 open
SYSML2-422 GenericToItemDefinition_Mapping should specialize GenericToOccurrenceDefinition_Mapping SysML 2.0b1 open
SYSML17-639 Element Name Incorrectly Shown as InternalBlockDiagram - Should be Dependency SysML 1.6 open
SYSML2-348 Incorrect item flow notation in example "Message" SysML 2.0b1 open
SYSML2-68 Graphical notation for nested reference usage needs resolution SysML 2.0a1 open
SYSML2-345 Incorrect inherited notation in example "Connection" SysML 2.0b1 open
SYSML2-347 Wrong reference usage notation SysML 2.0b1 open
SYSML2-343 Mistake in example "Part performs a reference action (action1) that references ..." SysML 2.0b1 open
SYSML2-344 Missing «perform action» in example "Part with Graphical Compartment with perform actions ..." SysML 2.0b1 open
SYSML2-342 Misleading port name in example "Part with Ports" SysML 2.0b1 open
SYSML2-340 Examples "Timeslices Compartment" and "Snapshots Compartment" incorrectly declare state feature SysML 2.0b1 open
SYSML2-341 Compartments still show nested feature notation SysML 2.0b1 open
SYSML2-339 Unnecessarily complicated examples "Timeslices Compartment" and "Snapshots Compartment" SysML 2.0b1 open
SYSML2-336 Incorrect notation in example "Individual Occurrence" SysML 2.0b1 open
SYSML2-338 Incomplete example "Occurrences Compartment" SysML 2.0b1 open
SYSML2-335 Incorrect keyword in example "Attributes Compartment" SysML 2.0b1 open
SYSML2-334 Incorrect example "Relationships Compartment" SysML 2.0b1 open
SYSML2-332 Incorrect example "Variant Membership" SysML 2.0b1 open
SYSML2-328 Incorrect private keyword notation SysML 2.0b1 open
SYSML2-330 Incorrect entry name representative notation SysML 2.0b1 open
SYSML2-322 Nesting parameter symbols should use rounded rectangles SysML 2.0b1 open
SYSML2-321 Nesting port symbols should use rounded rectangles SysML 2.0a1 open
SYSML2-319 Wrong line style on action flow succession SysML 2.0b1 open
SYSML2-287 sq-port-label and sq-ev-occurrence-label productions use Usage SysML 2.0a1 open
SYSML2-312 Typo: Table 19 - requirres SysML 2.0b1 open
SYSML2-47 Graphical BNF productions missing for connections SysML 2.0a1 open
SYSML2-397 TransitionUsage requires binding to succession with mandatory end multiplicities SysML 2.0b1 open
SYSML2-100 Semantics of a conditional succession using "else" are missing SysML 2.0a1 open
SYSML2-102 Semantic constraint for target of AssignmentActionUsage is missing SysML 2.0a1 open
SYSML2-393 Documentation of Time::defaultClock is missing SysML 2.0b1 open
SYSML2-390 Actor and subject parameter notation not effective SysML 2.0a1 open
SYSML2-55 Quantity and unit for ratio and fraction SysML 2.0a1 open
SYSML2-351 Unnecessary event declaration in example "Message" SysML 2.0b1 open
SYSML2-307 Various constraints need to take feature chaining into account SysML 2.0b1 open
SYSML2-199 Graphical notation of State Definition not consistent with other submission documents SysML 2.0a1 open
SYSML2-154 Subject of an include use case usage SysML 2.0a1 open
SYSML2-96 Incorrect action name in graphical notation example SysML 2.0a1 open
SYSML2-64 Flows compartment missing in Representative Notation Table SysML 2.0a1 open
SYSML2-95 Flows Compartment example graphical notation missing SysML 2.0a1 open
SYSML2-94 Confusing naming in Individual Occurrence example SysML 2.0a1 open
SYSML2-337 Incomplete example "Individual Occurrence" SysML 2.0b1 open
SYSML2-52 Examples requirement derivation, cause effect, and refinement missing SysML 2.0a1 open
SYSML2-51 Loop examples incomplete in representative notation table SysML 2.0a1 open
SYSML2-58 Representative notation table uses deprecated «equal» SysML 2.0a1 open
SYSML2-56 Missing graphical notation for n-ary connection def and usage SysML 2.0a1 open
SYSML2-49 Specification of standard geometric view missing SysML 2.0a1 open
SYSML2-33 Identify impact views on model organization SysML 2.0a1 open
SYSML2-38 Textual and graphical notations for flow on connection unclear SysML 2.0a1 open
SYSML2-157 Incorrect font in descriptions of AttributeUsage and TransitionUsage SysML 2.0a1 open
SYSML2-385 CommentAnnotation_Mapping shall be a "unique" mapping SysML 2.0a1 open
SYSML2-304 Mapping of ActivityEdge does not consider ActivityParameterNodes SysML 2.0b1 open
SYSML2-278 UntypedPin_Mapping redefines operation without any changes SysML 2.0a1 open
SYSML2-221 UML4SysML::Activities and StateMachines owned by blocks should be mapped to definition elements SysML 2.0a1 open
SYSML2-281 Map OpqueBehavior always to ActionDefinition SysML 2.0a1 open
SYSML2-258 Mapping of allcation between usage and definition or definition and usage elements does not work SysML 2.0a1 open
SYSML2-250 Typo in AEAReceiverFeatureValue_Mapping::value() SysML 2.0a1 open
SYSML2-248 CreateLinkObjectAction_Mapping should specialize CreateLinkAction_Mapping SysML 2.0a1 open
SYSML2-246 AEAParameterMembership_Mapping::ownedMemberParameter cannot return OclUndefined SysML 2.0a1 open
SYSML2-244 RVVAVariable_Mapping uses CommonAssignmentActionOwningMembership_Mapping, but should be a factory class SysML 2.0a1 open
SYSML2-241 TestCaseVerifyRequirementUsage_Mapping uses non-existing mapping classes SysML 2.0a1 open
SYSML2-240 TestCaseActivity_Mapping uses non-existing mapping classes SysML 2.0a1 open
SYSML2-238 ObjectFlows targeting a final node or a activity parameter node cannot be mapped SysML 2.0a1 open
SYSML2-236 Resolution of approved issue SYSML2-23 uses outdated mapping classes SysML 2.0a1 open
SYSML2-234 RSFAReferenceUsageFeatureMembership_Mapping uses non-existing mapping class SysML 2.0a1 open
SYSML2-229 ControlFlowSuccessionAsUsage_Mapping uses non-existing mapping class SysML 2.0a1 open
SYSML2-232 TIAOperatorExpression_Mapping uses non-existing mapping class EqualOperatorExpressionOperand_Mapping SysML 2.0a1 open
SYSML2-228 Helpers::activityOwnedRelationships mixes up FinalNodes and FlowFinalNodes SysML 2.0a1 open
SYSML2-206 Mapping of UML4SysML::InformationFlow with a realizing connector is not supported SysML 2.0a1 open
SYSML2-180 Mapping of UML4SysML::InformationFlow between definition elements is not supported SysML 2.0a1 open
SYSML2-181 Mapping of SysMLv1::ItemFlow does not consider the itemProperty SysML 2.0a1 open
SYSML2-378 Sample::calculation has an incorrect type SysML 2.0b1 open
SYSML2-326 Wrong imported package notation SysML 2.0b1 open
SYSML2-357 Representative example "Package with members" to be improved SysML 2.0b1 open
SYSML2-333 Incomplete textual notation in example "Variants Compartment" SysML 2.0b1 open
SYSML2-331 Incomplete textual notation in example "Subsetting" SysML 2.0b1 open
SYSML2-34 Missing graphical notation allocating flow to connection SysML 2.0a1 open
SYSML2-353 Feature modifiers missing in Portion Membership examples SysML 2.0b1 open
SYSML2-352 Feature modefiers missing in Feature Membership examples SysML 2.0b1 open
SYSML2-350 Incomplete flow notation in example "Flow as Node" SysML 2.0b1 open
SYSML2-349 Incorrect item flow notation in example "Interface as Node" SysML 2.0b1 open
SYSML2-329 Representative notation for filtered package import missing SysML 2.0b1 open
SYSML2-327 Package import wildcard is missing SysML 2.0b1 open
SYSML2-324 Missing representative notation for causation and requirements derivation SysML 2.0b1 open
SYSML2-323 Nesting parameter symbol is missing optional nested parameter SysML 2.0b1 open
SYSML2-320 Binding between action parameters and directed features on ports missing SysML 2.0b1 open
SYSML2-318 Adornments on ends missing in graphical syntax SysML 2.0b1 open
SYSML2-317 Metadata declaration needs clarification SysML 2.0b1 open
SYSML2-316 Symbol for metadata def is missing SysML 2.0b1 open
SYSML2-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-291 Case View is not a standard view SysML 2.0a1 open
SYSML2-255 Error in textual BNF for MessageDeclaration SysML 2.0a1 open
SYSML2-261 Error in textual BNF for TargetSuccession SysML 2.0a1 open
SYSML2-252 Graphical BNF opaque "text block" productions SysML 2.0a1 open
SYSML2-224 Number missing from table listing Standard View Definitions SysML 2.0a1 open
SYSML2-223 Table 38 "Standard View Definitions" redundant SysML 2.0a1 open
SYSML2-155 Limitation on specifying view renderings SysML 2.0a1 open
SYSML2-84 Connection declaration does not allow a feature value SysML 2.0a1 open
SYSML2-66 Graphical BNF for n-ary connections missing SysML 2.0a1 open
SYSML2-63 Various incorrect Graphical BNF productions SysML 2.0a1 open
SYSML2-62 Incorrect production for attributes-compartment-element SysML 2.0a1 open
SYSML2-46 Graphical BNF flow-label and interface-label productions missing SysML 2.0a1 open
SYSML2-44 Graphical BNF sq-message-label usage incorrect SysML 2.0a1 open
SYSML2-45 Graphical BNF interconnection view production incorrect SysML 2.0a1 open
SYSML2-43 Graphical BNF sq-message reference incorrect SysML 2.0a1 open
SYSML2-42 Textual production for sq-proxy-label incorrect SysML 2.0a1 open
SYSML2-39 Graphical BNF production sq-part refers to wrong port SysML 2.0a1 open
SYSML2-311 Transformation does not cover the mapping of Unit and QuantityKind SysML 2.0b1 open
SYSML2-309 Transformation does not cover mapping of Parameter::isStreaming=true SysML 2.0b1 open
SYSML2-305 Message and flow connection ends should be occurrence usages SysML 2.0b1 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
SYSML2-297 SysML Libraries' elements shall have an elementId defined SysML 2.0a1 open
SYSML2-295 Causation end features need to redefine source and target SysML 2.0a1 open
SYSML2-225 Some Standard View Definitions should be filtered specializations of General View SysML 2.0a1 open
SYSML2-60 Source and target on binary ConnectionDefinition symbol missing SysML 2.0a1 open
SYSML2-280 ElementMain_Mapping::ownedRelationship is wrong SysML 2.0a1 open
SYSML2-286 the getMapped operation cannot be called on ElementOwnership_Mapping SysML 2.0a1 open
SYSML2-284 Transformation does not cover UML4SysML::FunctionBehavior SysML 2.0a1 open
SYSML2-283 Transformation of UML4SysML::AcceptEventAction with more than one triggers not covered yet SysML 2.0a1 open
SYSML2-274 Transformation does not cover UML4SysML::DestroyLinkAction SysML 2.0a1 open
SYSML2-273 Transformation does not cover UML4SysML::CreateLinkAction SysML 2.0a1 open
SYSML2-272 Transformation does not cover UML4SysML::ReadLinkAction SysML 2.0a1 open
SYSML2-271 Transformation does not cover UML4SysML::SignalEvent SysML 2.0a1 open
SYSML2-65 Graphical BNF defines lifeline elements incorrectly SysML 2.0a1 open
SYSML2-41 Graphical BNF production proxy refers to wrong label SysML 2.0a1 open
SYSML2-40 Graphical BNF production sq-ev-occurrence has inconsistent proxy notation SysML 2.0a1 open
SYSML2-227 Subsections of section 7.7.2.3.7 should be ordered alphabetically 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-182 Universal features can have many values SysML 2.0a1 open
SYSML2-183 Some package-level features are mandatory SysML 2.0a1 open
SYSML2-185 ISQ in specification and libraries not aligned SysML 2.0a1 open
SYSML2-186 ConstraintBlock mapping parameters to input attributes SysML 2.0a1 open
SYSML2-177 Assignment action usages do not specify when their expressions are evaluated SysML 2.0a1 open
SYSML17-635 Risk, Source and Verification Method Are Attributes of Any / All Requirements Not Just an Extended Requirement SysML 1.5 open
SYSML2-226 Incorrect reference to SysML v1 to SysML v2 Transformation SysML 2.0a1 open
SYSML2-48 Consider production for standard case view vs filtered general view SysML 2.0a1 open
SYSML2-213 Typo in section 7.6.3 and section 7.6.4: mappingsto SysML 2.0a1 open
SYSML2-215 ControlFlow transformation target ends are not defined correctly SysML 2.0a1 open
SYSML2-197 ControlFlow target SuccessionAsUsage should have end feature with reference subsetting SysML 2.0a1 open
SYSML2-208 A ConnectionUsage should be owned by a FeatureMembership relationship SysML 2.0a1 open
SYSML2-202 Filter for mapping class Behavior_Mapping is useless SysML 2.0a1 open
SYSML2-204 Mapping of SysMLv1::ItemFlow does not consider the itemProperty SysML 2.0a1 open
SYSML2-211 Introduce GenericToTransitionUsage_Mapping class SysML 2.0a1 open
SYSML2-195 GenericToEndFeatureMembership_Mapping::to property redefines itself SysML 2.0a1 open
SYSML2-200 Description of Subsetting mapping classes is not correct SysML 2.0a1 open
SYSML2-178 ClassifierBehaviorFeatureMembership_Mapping does not exist SysML 2.0a1 open
SYSML2-174 EmptyReturnParameterFeatureMembership_Mapping does not exist SysML 2.0a1 open
SYSML2-189 ControlFlowSuccessionAsUsage_Mapping uses non existing mapping class ActivityEdgeInitialNodeSourceEndFeatureMembership_Mapping SysML 2.0a1 open
SYSML2-193 ControlFlowSuccessionAsUsage_Mapping uses non existing mapping class SysML 2.0a1 open
SYSML2-88 Mapping of allocation between usage elements is not specified yet SysML 2.0a1 open
SYSML2-171 Optimize Pin mapping class generalization hierarchy SysML 2.0a1 open
SYSML2-173 Mapping of ValueSpecificationActions does not work for untyped pins SysML 2.0a1 open
SYSML2-16 Subsections for mapping classes in section 7.7.2.3.9 should be ordered alphabetically SysML 2.0a1 open
SYSML2-19 REAOutputPin_Mapping should specialize OutputPin_Mapping SysML 2.0a1 open
SYSML2-14 UML4SysML::ClearVariableAction transformation does not include a ReturnParameter SysML 2.0a1 open
SYSML2-23 Transformation of UML4SysML::AddStructuralFeatureValueAction is not correct SysML 2.0a1 open
SYSML2-4 Transformation of UML4SysML::AddVariableValueAction is not correct SysML 2.0a1 open
SYSML2-2 ItemFlowEnds of ObjectFlow transformation target are not defined correctly SysML 2.0a1 open
SYSML2-18 Mapping of UML4SysML::RemoveVariableValueAction::isRemoveDuplicates is not covered SysML 2.0a1 open
SYSML2-188 Transformation of UML4SysML::InterruptibleActivityRegion is not specified yet SysML 2.0a1 open
SYSML2-106 Transformation of UML4SysML::ActivityFinalNode is not specified yet SysML 2.0a1 open
SYSML2-151 Transformation does not cover SysMLv1::NoBuffer SysML 2.0a1 open
SYSML2-150 Transformation does not cover SysMLv1::Overwrite SysML 2.0a1 open
SYSML2-128 Transformation does not cover UML4SysML::ActivityPartition SysML 2.0a1 open
SYSML2-107 Transformation does not cover UML4SysML::Extend SysML 2.0a1 open
SYSML2-105 Transformation of UML4SysML::DataStoreNode and UML4SysML::CentralBufferNode is not complete SysML 2.0a1 open
SYSML2-104 Transformation does not cover UML4SysML::GeneralizationSet SysML 2.0a1 open
SYSML2-219 Action::decisionTransitions should subset Action::transitions SysML 2.0a1 open
SYSML2-103 Editoral corrections in 7.16.11 SysML 2.0a1 open
SYSML2-156 Errors in textual BNF for RequirementDefinition and ConcernDefinition SysML 2.0a1 open
SYSML2-153 Error in assert constraint example SysML 2.0a1 open
SYSML2-92 Packages can also have compartments SysML 2.0a1 open
SYSML2-81 Association end name " /usageWithDirectedUsage" has a typo SysML 2.0a1 open
SYSML2-78 The .project.json file for the Cause and Effect Domain Library is misnamed SysML 2.0a1 open
SYSML2-69 Inefficient graphical notation specification tooling SysML 2.0a1 open
SYSML2-75 Spatial links can be occurrences SysML 2.0a1 open
SYSML2-26 Standard view filters incomplete SysML 2.0a1 open
SYSML2-54 Error in InterfaceUsage semantics subclause SysML 2.0a1 open
SYSML2-1 "Elements not mapped" table sections are empty SysML 2.0a1 open
SYSML2-7 Pin_Mapping::filter: property src should be from SysML 2.0a1 open
SYSML2-25 Standard view filters incomplete SysML 2.0a1 open
SYSML2-5 UntypedPin_Mapping::filter: property src should be from SysML 2.0a1 open
SYSML2-187 Transformation does not cover the different UML4SysML::PseudoStates SysML 2.0a1 open
SYSML2-91 XMI and JSON for model libraries SysML 2.0a1 open
SYSML2-161 XMI and JSON for example model SysML 2.0a1 open
SYSML2-160 Machine readable project interchange file(s) for language description examples SysML 2.0a1 open
SYSML2-159 Example analysis case fuelEconomyAnalysis SysML 2.0a1 open
SYSML2-158 Example FrontAxle definition SysML 2.0a1 open
SYSML2-152 Accepters on transition usages from entry actions SysML 2.0a1 open
SYSML2-149 Transformation does not cover SysMLv1::AllocateActivitiyPartition SysML 2.0a1 open
SYSML2-148 Transformation does not cover SysMLv1::PropertySpecificType SysML 2.0a1 open
SYSML2-147 Transformation does not cover SysMLv1::EndPathMultiplicity SysML 2.0a1 open
SYSML2-146 Transformation does not cover SysMLv1::ParticipantProperty SysML 2.0a1 open
SYSML2-145 Transformation does not cover SysMLv1::BoundReference SysML 2.0a1 open
SYSML2-144 Transformation does not cover SysMLv1::DistributedProperty SysML 2.0a1 open
SYSML2-143 Transformation does not cover SysMLv1::Expose SysML 2.0a1 open
SYSML2-142 Transformation does not cover SysMLv1::Conform SysML 2.0a1 open
SYSML2-141 Transformation does not cover SysMLv1::View SysML 2.0a1 open
SYSML2-140 Transformation does not cover SysMLv1::InvocationOnNestedPortAction SysML 2.0a1 open
SYSML2-139 Transformation does not cover SysMLv1::~InterfaceBlock SysML 2.0a1 open
SYSML2-138 Transformation does not cover SysMLv1::FlowProperty SysML 2.0a1 open
SYSML2-137 Transformation does not cover SysMLv1::AddFlowPropertyValueOnNestedPortAction SysML 2.0a1 open
SYSML2-136 Transformation does not cover SysMLv1::ChangeStructuralFeatureEvent SysML 2.0a1 open
SYSML2-135 Transformation does not cover SysMLv1::TriggerOnNestedPort SysML 2.0a1 open
SYSML2-134 Transformation does not cover UML4SysML::UnmarshallAction SysML 2.0a1 open
SYSML2-133 Transformation does not cover UML4SysML::LinkEndData SysML 2.0a1 open
SYSML2-132 Transformation does not cover UML4SysML::LinkEndDestructionData SysML 2.0a1 open
SYSML2-131 Transformation does not cover UML4SysML::LinkEndCreationData SysML 2.0a1 open
SYSML2-130 Transformation does not cover UML4SysML::ConditionalNode SysML 2.0a1 open
SYSML2-129 Transformation does not cover UML4SysML::Clause SysML 2.0a1 open
SYSML2-127 Transformation does not cover UML4SysML::InteractionConstraint SysML 2.0a1 open
SYSML2-126 Transformation does not cover UML4SysML::OccurrenceSpecification SysML 2.0a1 open
SYSML2-125 Transformation does not cover UML4SysML::Gate SysML 2.0a1 open
SYSML2-124 Transformation does not cover UML4SysML::ExecutionOccurrenceSpecification SysML 2.0a1 open
SYSML2-123 Transformation does not cover UML4SysML::ConsiderIgnoreFragment SysML 2.0a1 open
SYSML2-122 Transformation does not cover UML4SysML::PartDecomposition SysML 2.0a1 open
SYSML2-121 Transformation does not cover UML4SysML::GeneralOrdering SysML 2.0a1 open
SYSML2-120 Transformation does not cover UML4SysML::Continuation SysML 2.0a1 open
SYSML2-119 Transformation does not cover UML4SysML::DestructionOccurrenceSpecification SysML 2.0a1 open
SYSML2-118 Transformation does not cover UML4SysML::Image SysML 2.0a1 open
SYSML2-117 Transformation does not cover UML4SysML::Interval SysML 2.0a1 open
SYSML2-116 Transformation does not cover UML4SysML::TimeConstraint SysML 2.0a1 open
SYSML2-115 Transformation does not cover UML4SysML::DurationInterval SysML 2.0a1 open
SYSML2-114 Transformation does not cover UML4SysML::StringExpression SysML 2.0a1 open
SYSML2-113 Transformation does not cover UML4SysML::DurationObservation SysML 2.0a1 open
SYSML2-112 Transformation does not cover UML4SysML::IntervalConstraint SysML 2.0a1 open
SYSML2-111 Transformation does not cover UML4SysML::TimeObservation SysML 2.0a1 open
SYSML2-110 Transformation does not cover UML4SysML::Duration SysML 2.0a1 open
SYSML2-109 Transformation does not cover UML4SysML::DurationConstraint SysML 2.0a1 open
SYSML2-108 Transformation does not cover UML4SysML::TimeInterval SysML 2.0a1 open
SYSML2-98 Port transfer semantics SysML 2.0a1 open
SYSML2-97 Semantics of transfers across interfaces SysML 2.0a1 open
SYSML2-87 Add standard domain libraries for mathematical and physical constants SysML 2.0a1 open
SYSML2-85 Effective name is not correct for a redefined perform action usage SysML 2.0a1 open
SYSML2-83 Narrow down return types of SpatialItem::PositionOf and ::CurrentPositionOf SysML 2.0a1 open
SYSML2-82 Extend ISQ with missing quantity and unit types for US Customary Units SysML 2.0a1 open
SYSML2-80 Reflective SysML abstract syntax model has inconsistencies SysML 2.0a1 open
SYSML2-79 View::viewpointSatisfactions should subset viewpointChecks and checkedConstraints SysML 2.0a1 open
SYSML2-77 Resolve "TODO" in domain library model Time SysML 2.0a1 open
SYSML2-37 Identify the owning context in a graphical view SysML 2.0a1 open
SYSML2-36 Regularization of textual notation for loops SysML 2.0a1 open
SYSML2-35 Missing explicit explanation of compartments as views SysML 2.0a1 open
SYSML2-32 Clarify query using view SysML 2.0a1 open
SYSML2-31 Icons for standard view definitions missing SysML 2.0a1 open
SYSML2-71 Graphical BNF for grid rendering is missing SysML 2.0a1 open
SYSML2-70 Graphical notation for variant inheritance from variation requires improvement SysML 2.0a1 open
SYSML2-67 Graphical BNF mapping to abstract syntax is missing SysML 2.0a1 open
SYSML2-61 Special graphical notation for distinguished parameters in name compartment SysML 2.0a1 open
SYSML2-59 Graphical notation for edges is not 100% consistent SysML 2.0a1 open
SYSML2-53 Parameter symbol notation needs improvement SysML 2.0a1 open
SYSML2-57 Port symbol notation (arrows) needs improvement SysML 2.0a1 open
SYSML2-50 No support for metadata in graphical notation SysML 2.0a1 open
SYSML2-30 Follow typographical conventions in the SysML Metamodel clause SysML 2.0a1 open
SYSML2-29 Name all associations in the SysML abstract syntax SysML 2.0a1 open
SYSML2-21 RSAOutputPin_Mapping should specialize OutputPin_Mapping SysML 2.0a1 open
SYSML2-17 Incomplete description of TestCaseVerifyObjectiveMembership_Mapping SysML 2.0a1 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

Text error in List property construction

  • Key: SYSML2-453
  • Status: open  
  • Source: Georgia Institute of Technology ( Richard Wallace)
  • Summary:

    The production for <SourceSuccessionMember > has "" and it should be "="

    SourceSuccessionMember : FeatureMembership =
    'then' ownedRelatedElement + SourceSuccession

    The production for <SourceEndMember> has "" and it should be "="

    SourceEndMember : EndFeatureMembership =
    ownedRelatedElement + SourceEnd

  • Reported: SysML 2.0b1 — Wed, 13 Sep 2023 18:02 GMT
  • Updated: Mon, 18 Sep 2023 16:40 GMT

PrefixComment should not be a production for AnnotatingElement

  • Key: SYSML2-454
  • Status: open  
  • Source: Georgia Institute of Technology ( Richard Wallace)
  • Summary:

    The option for <PrefixComment> has been deprecated, but is still an option for AnnotatingElement. Remove PrefixComment.

    AnnotatingElement =
    Comment
    | PrefixComment
    | Documentation
    | TextualRepresentation
    | MetadataUsage
    
  • Reported: SysML 2.0b1 — Wed, 13 Sep 2023 20:34 GMT
  • Updated: Mon, 18 Sep 2023 16:39 GMT

misspelled ConjugatePortTyping should be ConjugatedPortTyping

  • Key: SYSML2-452
  • Status: open  
  • Source: Georgia Institute of Technology ( Richard Wallace)
  • Summary:

    Prior error report on this production can be replaced with this error report.

    The issue is with the production:

    FeatureTyping = <OwnedFeatureTyping> | <ConjugatePortTyping>

    The correct conjugate nonterminal should be <ConjugatedPortTyping>

  • Reported: SysML 2.0b1 — Tue, 12 Sep 2023 21:27 GMT
  • Updated: Mon, 18 Sep 2023 16:38 GMT

Missing production for ConjugatePortTyping

  • Key: SYSML2-451
  • Status: open   Implementation work Blocked
  • Source: Georgia Institute of Technology ( Richard Wallace)
  • Summary:

    In the production:

    FeatureTyping = <OwnedFeatureTyping> | <ConjugatePortTyping>

    There is no corresponding production for the non-terminal <ConjugatePortTyping>.
    <ConjugatedPortDefinitionMember> or <ConjugatedPortDefinition> may be correct for <FeatureTyping>.

  • Reported: SysML 2.0b1 — Tue, 12 Sep 2023 21:01 GMT
  • Updated: Mon, 18 Sep 2023 16:37 GMT

Incorrect EBNF specification

  • Key: SYSML2-431
  • Status: open  
  • Source: Georgia Institute of Technology ( Richard Wallace)
  • Summary:

    The current specification:
    "SourceSuccessionMember : FeatureMembership =
    'then' ownedRelatedElement + SourceSuccession

    SourceSuccession : SuccessionAsUsage =
    ownedRelationship += SourceEndMember

    SourceEndMember : EndFeatureMembership =
    ownedRelatedElement + SourceEnd"

    is incorrect. It should be:

    "SourceSuccessionMember : FeatureMembership =
    'then' ownedRelatedElement += SourceSuccession

    SourceSuccession : SuccessionAsUsage =
    ownedRelationship += SourceEndMember

    SourceEndMember : EndFeatureMembership =
    ownedRelatedElement += SourceEnd"

  • Reported: SysML 2.0b1 — Sat, 2 Sep 2023 13:29 GMT
  • Updated: Wed, 13 Sep 2023 22:37 GMT

Document how SysML v1 properties are mapped to SysML v2

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

    The SysML v1 properties like part property, are concepts, but not stereotypes or metamodel elements. Therefore, they are explicitly covered by a mapping class or are listed in the overview tables.

    Add a documentation in section 7.8.4.1 that describes how the different SysML v1 property concepts are mapped to SysML v2.

  • Reported: SysML 2.0b1 — Sun, 10 Sep 2023 16:32 GMT
  • Updated: Wed, 13 Sep 2023 14:22 GMT

Property_Mapping should map to ItemUsage and the class name is misleading

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

    Property_Mapping maps properties typed by a Class or Interface. The target element should be ItemUsage instead of Feature.

    The name of the mapping class is misleading. It creates the impression that it maps all kinds of properties, but it only covers the cases where a Class or Interface types properties. Rename the mapping class to PropertyTypedByClassInterface_Mapping.

    The specialized mapping classes ConstraintParameter_Mapping, Port_Mapping, and Part_Mapping should specialize PropertyCommon_Mapping instead of Property_Mapping.

  • Reported: SysML 2.0b1 — Sun, 10 Sep 2023 10:33 GMT
  • Updated: Wed, 13 Sep 2023 14:20 GMT

Decision/MergeNode SuccessionSpecialization checks missing some constraints

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

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

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

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

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

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

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

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

  • Reported: SysML 2.0b1 — Wed, 16 Aug 2023 17:21 GMT
  • Updated: Tue, 12 Sep 2023 15:51 GMT

Fork/JoinNode succession "other" end multiplicity validations missing

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

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

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

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

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

  • Reported: SysML 2.0b1 — Tue, 12 Sep 2023 15:26 GMT
  • Updated: Tue, 12 Sep 2023 15:26 GMT

Description of TimeEvent_Mapping is a note

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

    The description of the TimeEvent_Mapping class is a note from the development team instead of a description text.

  • Reported: SysML 2.0b1 — Thu, 31 Aug 2023 10:34 GMT
  • Updated: Tue, 12 Sep 2023 11:44 GMT

TimeEvent should be mapped to an accept action instead of TextualRepresentation

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

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

  • Reported: SysML 2.0b1 — Tue, 12 Sep 2023 11:42 GMT
  • Updated: Tue, 12 Sep 2023 11:44 GMT

Description of ChangeEvent_Mapping is a note

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

    The description of the ChangeEvent_Mapping class is a note from the development team instead of a description text.

  • Reported: SysML 2.0b1 — Thu, 31 Aug 2023 10:31 GMT
  • Updated: Tue, 12 Sep 2023 11:39 GMT

ChangeEvent should be mapped to an accept action instead of TextualRepresentation

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

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

  • Reported: SysML 2.0b1 — Tue, 12 Sep 2023 11:35 GMT
  • Updated: Tue, 12 Sep 2023 11:38 GMT

LoopActionUsage descriptions refer to property not in metamodel

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

    The descriptions in 8.3.16.9 (ForLoopActionUsage) and 8.3.16.18 (WhileLoopsActionusage) refer to "bodyClause", but in Figure 28 (Structured Control Actions) the association end for this (presumably) is called "bodyAction".

  • Reported: SysML 2.0b1 — Thu, 31 Aug 2023 15:09 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

WhileLoopsActionusage title typos

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

    The title of 8.3.16.18 is WhileLoopsActionusage, with plural "Loops" and lower case "u", but in Figure 28 (Structured Control Actions) these are singular and capitalized, respectively.

  • Reported: SysML 2.0b1 — Thu, 31 Aug 2023 14:59 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

checkIfActionUsageSpecialization OCL specifiesFromLibrary typo

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

    In 8.3.16.10 (IfActionUsage), the OCL for checkIfActionUsageSpecialization refers to specifiesFromLibrary instead of specializesFromLibrary.

  • Reported: SysML 2.0b1 — Thu, 31 Aug 2023 14:51 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

TransitionUsage effectAction attribute text and constraint are different

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

    In Clause 8.3.17.9 (TransitionUsage), the Attributes section says effectAction are expressions:

    Attributes
    /effectAction : ActionUsage [0..*] {subsets feature}
    The ActionUsages that define the effects of this TransitionUsage, which are the ownedFeatures of the TransitionUsage related to it by TransitionFeatureMemberships with kind = effect, which must all be Expressions.

    but a constraint says they're action usages

    deriveTransitionUsageEffectAction
    The effectActions of a TransitionUsage are the transitionFeatures of the ownedFeatureMemberships of the TransitionUsage with kind = effect, which must all be ActionUsages.
    triggerAction = ownedFeatureMembership->
    selectByKind(TransitionFeatureMembership)->
    select(kind = TransitionFeatureKind::trigger).transitionFeatures->
    selectByKind(AcceptActionUsage)

  • Reported: SysML 2.0a1 — Fri, 25 Aug 2023 19:39 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

checkTransitionUsageSourceBindingConnector text and OCL are different

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

    In 8.3.17.9 (TransitionUsage), the text for checkTransitionUsageSourceBindingConnector requires binding of the first input parameter

    A TransitionUsage must have an ownedMember that is a BindingConnector between its source and its first input parameter (which redefines Actions::TransitionAction::transitionLinkSource).

    while the OCL gives it as binding the second parameter

    ownedMember->selectByKind(BindingConnector)->exists(b |
    b.relatedFeatures->includes(source) and
    b.relatedFeatures->includes(inputParameter(2)))

  • Reported: SysML 2.0b1 — Tue, 29 Aug 2023 18:07 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

The OCL for the body of ConstraintUsage::namingFeature is incorrect

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

    The body OCL for the namingFeature operation of ConstraintUsage references ownedFeatureMembership. This should instead be owningFeatureMembership.

  • Reported: SysML 2.0b1 — Thu, 3 Aug 2023 14:22 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

validateStateDefinitionIsParallelGeneralization and validateStateUsageIsParallelGeneralization OCL is wrong

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

    The OCL for the constraints validateStateDefinitionIsParallelGeneralization and validateStateUsageIsParallelGeneralization both use ownedGeneralization (which doesn't exist) instead of ownedSpecialization.

  • Reported: SysML 2.0b1 — Fri, 14 Jul 2023 19:23 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

validateStateDefinitionIsParallelGeneralization and validateStateUsageIsParallelGeneralization constraints are too restrictive

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

    The validateStateDefinitionIsParallelGeneralization and validateStateUsageIsParallelGeneralization prohibit parallel state definitions and usages from owning specializations of non-parallel state definitions and usages (and vice versa). However, this would prevent even, e.g., an empty non-parallel state definition from having a usage that was parallel, for example:

    state def S;
    state s : S parallel {  // validation error!
        state s1;
        state s2;
    }
    

    Further, it is also a validation error for a parallel state definition to explicitly specialized the base state definition StateAction (which is not parallel), even though an implicit specialization is not checked:

    state def S1 parallel { } // legal, implicitly specializes StateAction
    state def S2 :> States::StateAction parallel { } // validation error!
    

    For consistency, it would seem that, at least, a parallel state definition or usage should be able to explicitly specialize a non-parallel one. But perhaps the constraints are really not semantically necessary at all.

  • Reported: SysML 2.0b1 — Sun, 16 Jul 2023 21:17 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

validateOccurrenceUsageIndividualDefinition OCL is wrong

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

    The OCL for the constraint validateOccurrenceUsageIndividualDefinition is

    occurrenceDefinition->select(isIndividual).size() <= 1
    

    However, the type of OccurrenceUsage::occurrenceDefinition is actually Class, not OccurrenceDefinition, but the property isIndividual is only defined on OccurrenceDefinition.

  • Reported: SysML 2.0b1 — Fri, 14 Jul 2023 18:26 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

validateUsageOwningType constraint is too restrictive

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

    The constraint validateUsageOwningType constrains the owningType of a Usage to be a Definition or Usage. However, this is two restrictive, because it prevents, e.g., a Usage from being declared within a body expression (as used with collect, select, etc.), which is a KerML Expression.

  • Reported: SysML 2.0b1 — Fri, 14 Jul 2023 16:26 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

validateDefinitionVariationSpecialization and validateUsageVariationSpecialization OCL is wrong

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

    The OCL for both of the constraints validateDefinitionVariationSpecialization and validateUsageVariationSpecialization is:

    isVariation implies
        not ownedSpecialization.specific->exists(isVariation)
    

    These constraints should be checking Specialization::general, not Specialization::specific. In addition, the type of both specific and general is Type, which doesn't have an isVariation property. Only Definition and Usage types have such a property.

  • Reported: SysML 2.0b1 — Fri, 14 Jul 2023 15:50 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

validateDefinitionNonVariationMembership and validateUsageNonVariationMembership are redundant with validateVariantMembershipOwningNamespace

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

    The constraints validateDefinitionNonVariationMembership and validateUsageNonVariationMembership check that a non-variation Definition or Usage owns no VariantMemberships. However, validateVariantMembershipOwningNamespace already checks that the membershipOwningNamespace of a VariantMembership is a variation, so the other constraints are redundant.

  • Reported: SysML 2.0b1 — Fri, 14 Jul 2023 16:23 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

validateDefinitionVariationMembership and validateUsageVariationMembership are too strict

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

    The constraints validateDefinitionVariationMembership and validationUsageVariationMembership require that all the owned members of a variation definition or usage be variant members. This is too strong:

    • It disallows any variation Usage from having a Multiplicity, because that is a non-variant owned member of the Usage.
    • It disallows a variation PortDefinition from having a required ConjugatedPortDefinition, because that is a non-variant owned member of the definition.
  • Reported: SysML 2.0b1 — Thu, 13 Jul 2023 20:20 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

Redundant numbered list in language description of usage

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

    Toward the end of subclause 7.6.3 Usage of the SysML v2 specification, there is a numbered list describing additional keywords that can be used in a usage declaration. However, this list is repeated twice (sequentially, one right after the other). The two lists are consistent, but the second one is more complete, so the first list is redundant.

  • Reported: SysML 2.0a1 — Mon, 26 Jun 2023 17:18 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

validateFramedConcernUsageConstraintKind constraint is misnamed

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

    The constraint validateFramedConcernUsageConstraintKind is owned by FramedConcernMembership, not FramedConcernUsage (which doesn't exist). Therefore, the constraint should be named validateFramedConcernMembershipConstraintKind.

  • Reported: SysML 2.0b1 — Thu, 13 Jul 2023 02:38 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

Additional cases when usages are required to be referential

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

    The following statements are made in Clause 7 (Language Description) of the SysML v2 specification:

    • Subclause 7.6.3 (Usages): "Note also that a directed usage is always referential, whether or not the keyword ref is also given explicitly in its declaration."
    • Subclause 7.13.2 (Connection Definitions and Usages): "The end features of a connection definition or usage are always considered referential (non-composite), whether or not their declaration explicitly includes the ref keyword."

    However, there are currently no constraints on the Usage class in the abstract syntax to enforce these rules (see 8.3.6.4).

    In addition, a usage that is not explicitly declared as a feature of a type is, by default, considered to be a feature of the base type Anything. However, since Anything is not a kind of Occurrence, its features cannot be composite. Therefore, such usages should be always referential.

  • Reported: SysML 2.0a1 — Mon, 26 Jun 2023 17:15 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

Errors in TransitionUsage semantic constraints

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

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

    checkTransitionUsageSpecialization

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

    checkTransitionUsageActionSpecialization

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

deriveForLoopActionUsageBodyAction is misnamed

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

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

  • Reported: SysML 2.0a1 — Mon, 8 May 2023 21:53 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

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

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

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 22:22 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

The description and derivation of ForLoopActionUsage::seqArgument is wrong

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

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

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

    The second sentence is clearly wrong. It should instead be

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

    Similarly, the description of the constraint deriveForLoopActionUsageSeqArgument should be

    The seqArgument of a ForLoopActionUsage is its first argument Expression.

    and with the OCL

    seqArgument = argument(1)

  • Reported: SysML 2.0a1 — Mon, 8 May 2023 21:50 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

Incorrect notation in action examples

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

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

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

    and

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

    These should be

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

    and

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

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

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

    This should instead be something like:

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 21:33 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

Validation constraints are missing in the SysML abstract syntax

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

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

    8.3.16.5 AssignmentActionUsage

    validateAssignmentActionUsageArguments – An AssignmentActionUsage must have two argument Expressions.

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

    8.3.16.9 ForLoopActionUsage

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

    validateForLoopActionUsageParameters – A ForLoopActionUsage must have two owned input parameters.

    8.3.16.10 IfActionUsage

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

    8.3.16.16 TriggerInvocationExpression

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

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

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

    8.3.16.18 WhileLoopActionUsage

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

    8.3.17.2 ExhibitStateUsage

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

    8.3.19.2 AssertConstraintUsage

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

    8.3.20.10 SatisfyRequirementUsage

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

    8.3.24.2 IncludeUseCaseUsage

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

  • Reported: SysML 2.0a1 — Tue, 25 Apr 2023 20:50 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

Wrong compartment name: documentation

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

    In example "Documentation Compartment", the documentation keyword should read doc

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:56 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

Keyword for documentation is "doc"

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

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 20:59 GMT
  • Updated: Tue, 12 Sep 2023 01:00 GMT

UML4SysML::Class should be mapped to ItemDefinition

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

    UML4SysML::Class is currently mapped to OccurrenceDefinition, but should be ItemDefinition.

  • Reported: SysML 2.0b1 — Fri, 8 Sep 2023 17:45 GMT
  • Updated: Mon, 11 Sep 2023 06:15 GMT

Change the table header of the overview tables in the mapping class specification chapters

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

    The table headers state that the rows list SysML v1 and v2 concepts. Actually, they only list stereotype and metamodel elements but not all the concepts. For example, the part property is not listed because it is not a SysML v1 stereotype but only a concept.

  • Reported: SysML 2.0b1 — Sat, 9 Sep 2023 11:59 GMT
  • Updated: Sun, 10 Sep 2023 18:49 GMT

InformationFlow mapping classes should use GenericTo mapping classes

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

    The mapping classes InformationFlowEnd_Mapping, InformationFlowFeatureTyping_Mapping, and InformationFlowEndFeatureMembership_Mapping updated by SYSML2-180 should use more specialized GenericTo mapping classes instead of the GenericToElement_Mapping class:

    InformationFlowEnd_Mapping => GenericToFeature_Mapping
    InformationFlowFeatureTyping_Mapping => GenericToFeatureTyping_Mapping
    InformationFlowEndFeatureMembership_Mapping => GenericToFeatureMembership_Mapping

  • Reported: SysML 2.0b1 — Thu, 31 Aug 2023 11:32 GMT
  • Updated: Sun, 10 Sep 2023 18:49 GMT

SYSML2-180 uses non-existing general mapping class GenericToItemUsage_Mapping

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

    The approved resolution for issue SYSML2-180 uses the mapping class GenericToItemUsage_Mapping which does not exist. It seems that it was overseen to add the creation of the mapping class to the revised text of the resolution.

  • Reported: SysML 2.0b1 — Tue, 29 Aug 2023 13:22 GMT
  • Updated: Sun, 10 Sep 2023 18:49 GMT

The transformation specification does not explicitly specify how to map a ValueType

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

    The mapping of a ValueType is identical to the mapping of a DataType. Therefore, there is no explicit mapping class for ValueType. However, that hides the information of the mapping of ValueTypes in the transformation specification.

  • Reported: SysML 2.0b1 — Fri, 8 Sep 2023 16:08 GMT
  • Updated: Sun, 10 Sep 2023 18:49 GMT

Part properties with AggregationKind::none or shared are not mapped to PartUsage with isComposite=false

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

    Part properties with AggregationKind::none or shared are mapped to Feature, but should be a PartUsage with isComposite=false.

  • Reported: SysML 2.0b1 — Fri, 8 Sep 2023 15:23 GMT
  • Updated: Sun, 10 Sep 2023 18:49 GMT

ConstraintProperty should be mapped to a AssertConstraintUsage

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

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

  • Reported: SysML 2.0b1 — Sun, 10 Sep 2023 16:27 GMT
  • Updated: Sun, 10 Sep 2023 16:27 GMT

Incorrect notation in example "Binding Connection"

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

    In example "Binding Connection" «ref part» part4R should use the graphical notation as specified in the graphical BNF in subclause 8.2.3.11.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:31 GMT
  • Updated: Wed, 6 Sep 2023 12:15 GMT

Subsetting of subjectParameter properties is wrong

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

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

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

  • Reported: SysML 2.0b1 — Mon, 4 Sep 2023 18:27 GMT
  • Updated: Tue, 5 Sep 2023 19:06 GMT

specializesFromLibrary arguments use inconsistent notation for strings

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

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

  • Reported: SysML 2.0b1 — Thu, 31 Aug 2023 15:35 GMT
  • Updated: Thu, 31 Aug 2023 15:55 GMT

GenericToItemDefinition_Mapping should specialize GenericToOccurrenceDefinition_Mapping

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

    The generic mapping class GenericToItemDefinition_Mapping specializes GenericToDefinition_Mapping. However, it should specialize GenericToOccurrenceDefinition_Mapping which is a subclass of GenericToDefinition_Mapping as well as ItemDefinition specializes OccurrenceDefinition.

  • Reported: SysML 2.0b1 — Thu, 31 Aug 2023 13:59 GMT
  • Updated: Thu, 31 Aug 2023 15:39 GMT

Element Name Incorrectly Shown as InternalBlockDiagram - Should be Dependency

  • Status: open  
  • Source: Eclectica Systems Ltd ( Nic Plum)
  • Summary:

    The first row of Table 8-4 shows element InternalBlockDiagram - for a connector whose Abstract Syntax ref is UML4SysML::Dependency.

    This is incorrect - it should be a Dependency connector element - identical to first row in Table 8-2

  • Reported: SysML 1.6 — Tue, 29 Aug 2023 13:23 GMT
  • Updated: Wed, 30 Aug 2023 15:28 GMT


Graphical notation for nested reference usage needs resolution

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

    According to the Graphical BNF, the notation for a nested reference usage is now a white diamond in the upper-right hand corner of the usage shape (or optionally a black diamond for a non-reference usage, which is the default). In the Graphical BNF productions this is represented by rd = (reference-diamond)? as defined in clause 8.2.3.6. This is a change from the previous dashed-outline shape as also used in SysML v1.

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

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

    After discussion the Graphical Specification WG recommends to replace the upper-right-hand corner reference-diamond notation with a dotted-outline for reference usage, and stay with a solid-outline for composite usage.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 15:16 GMT
  • Updated: Wed, 30 Aug 2023 00:34 GMT

Incorrect inherited notation in example "Connection"

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

    In example "Connection" (1) remove circumflex on end1 and end2, since they are (implicitly) redefinitions of the ends from the connection definition, not inherited features.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:29 GMT
  • Updated: Wed, 30 Aug 2023 00:34 GMT
  • Attachments:

Wrong reference usage notation

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

    Replace nested reference usage notation with dotted outline notation. Add BNF production for this notation.
    Reference usage notation is used in interconnection diagrams, and potentially action flow diagram. The solution is to add explicit production for dotted usages of parts, constraints, and requirements references and include those production in interconnection diagrams. Create productions of action usage references and add them to action flow.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:37 GMT
  • Updated: Wed, 30 Aug 2023 00:34 GMT

Mistake in example "Part performs a reference action (action1) that references ..."

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

    In example "Part performs a reference action (action1) that reference subsets another action (action3)" replace «perform action» action1 with «perform» action2, and «action» action3 : Action3 with «action» action2 : Action2, and adapt the textual notation accordingly. This also makes it consistent with the preceding example.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:26 GMT
  • Updated: Wed, 30 Aug 2023 00:34 GMT

Missing «perform action» in example "Part with Graphical Compartment with perform actions ..."

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

    In example "Part with Graphical Compartment with perform actions and flows between them." add «perform action» to both action2 and action3.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:28 GMT
  • Updated: Wed, 30 Aug 2023 00:34 GMT
  • Attachments:

Misleading port name in example "Part with Ports"


Examples "Timeslices Compartment" and "Snapshots Compartment" incorrectly declare state feature

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

    In examples "Timeslices Compartment" and "Snapshots Compartment" remove state state1 feature, since it is confusing, and potentially incorrect.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:20 GMT
  • Updated: Wed, 30 Aug 2023 00:34 GMT

Compartments still show nested feature notation

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

    Remove nested features (textual) notation from compartments in graphical symbols in all Representative Notation tables where they occur. This capability was discarded.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:24 GMT
  • Updated: Wed, 30 Aug 2023 00:34 GMT

Unnecessarily complicated examples "Timeslices Compartment" and "Snapshots Compartment"


Incorrect notation in example "Individual Occurrence"

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

    Example "Individual Occurrence" should include individual def from preceding example, and rename occurrence1 to occurrence1-1.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:16 GMT
  • Updated: Wed, 30 Aug 2023 00:34 GMT
  • Attachments:

Incomplete example "Occurrences Compartment"


Incorrect keyword in example "Attributes Compartment"

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

    In example "Attributes Compartment" textual notation should use nonunique instead of unique.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:16 GMT
  • Updated: Wed, 30 Aug 2023 00:34 GMT

Incorrect example "Relationships Compartment"

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

    In example "Relationships Compartment" add textual notation that matches the graphical notation. Also "connect part3" in second symbol should be removed.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:14 GMT
  • Updated: Wed, 30 Aug 2023 00:34 GMT
  • Attachments:

Incorrect example "Variant Membership"

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

    In example "Variant Membership" the variants should be defined by Part1a and Part1b respectively. Currently they are both defined by Part1.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:12 GMT
  • Updated: Wed, 30 Aug 2023 00:34 GMT
  • Attachments:

Incorrect private keyword notation

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

    Example "Package with imported packages (nested packages)" should have «private» enclosed by guillemets

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:59 GMT
  • Updated: Wed, 30 Aug 2023 00:34 GMT
  • Attachments:

Incorrect entry name representative notation

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

    Example "Usage Definition" should be labeled "Part defined by Part Definition"

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:11 GMT
  • Updated: Wed, 30 Aug 2023 00:34 GMT


Nesting port symbols should use rounded rectangles


Wrong line style on action flow succession

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

    A succession relationship on an action flow should be a solid line with an open arrow head. In 7.16.1 in example "Accept and Send Action Flow". Check for other locations.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:13 GMT
  • Updated: Wed, 30 Aug 2023 00:34 GMT
  • Attachments:

sq-port-label and sq-ev-occurrence-label productions use Usage

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

    In 8.2.3.9, the sq-port-port-label and sq-ev-occurrence-label use Usage from the textual BNF. But Usage includes UsageBody, which was not intended to be included in this graphical notation.

  • Reported: SysML 2.0a1 — Sun, 9 Jul 2023 22:57 GMT
  • Updated: Wed, 30 Aug 2023 00:34 GMT

Typo: Table 19 - requirres

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

    Table 19, Requirement, compartment for require constraints:

    Typo in compartment headline should be "require constraints" => "requirre"

  • Reported: SysML 2.0b1 — Sun, 23 Jul 2023 19:11 GMT
  • Updated: Wed, 30 Aug 2023 00:34 GMT
  • Attachments:

Graphical BNF productions missing for connections


TransitionUsage requires binding to succession with mandatory end multiplicities

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

    Clause 7.13.3 (Bindings as Usages) says

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

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

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

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

  • Reported: SysML 2.0b1 — Fri, 25 Aug 2023 19:22 GMT
  • Updated: Tue, 29 Aug 2023 18:52 GMT

Semantics of a conditional succession using "else" are missing

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

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

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

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

    DefaultTargetSuccession : TransitionUsage =
        'else' ownedRelationship += TransitionSuccessionMember
    

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 22:10 GMT
  • Updated: Tue, 29 Aug 2023 17:40 GMT

Semantic constraint for target of AssignmentActionUsage is missing

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

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

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

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 22:28 GMT
  • Updated: Mon, 28 Aug 2023 16:44 GMT

Documentation of Time::defaultClock is missing

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

    Subclause 9.8.8 on the Time package in the Quantities and Units Domain Library does not include documentation of defaultClock, which is in the normative library model.

  • Reported: SysML 2.0b1 — Thu, 24 Aug 2023 14:55 GMT
  • Updated: Thu, 24 Aug 2023 14:55 GMT

Actor and subject parameter notation not effective

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

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

  • Reported: SysML 2.0a1 — Thu, 24 Aug 2023 12:11 GMT
  • Updated: Thu, 24 Aug 2023 14:52 GMT

Quantity and unit for ratio and fraction

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

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

    Similarly fraction, FractionValue and FractionUnit would be useful.

    Add these concepts as specializations of DimensionOneValue and DimensionOneUnit.

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 23:17 GMT
  • Updated: Thu, 24 Aug 2023 03:18 GMT

Unnecessary event declaration in example "Message"

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

    In (the second) example "Message" the event details should be removed from textual notation. The message becomes message msg1 from a1 to a2 in textual notation.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:44 GMT
  • Updated: Wed, 23 Aug 2023 22:13 GMT

Various constraints need to take feature chaining into account

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

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

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

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

  • Reported: SysML 2.0b1 — Sun, 16 Jul 2023 21:30 GMT
  • Updated: Wed, 23 Aug 2023 22:05 GMT

Graphical notation of State Definition not consistent with other submission documents

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

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

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

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

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

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

  • Reported: SysML 2.0a1 — Fri, 12 May 2023 08:13 GMT
  • Updated: Wed, 23 Aug 2023 21:53 GMT

Subject of an include use case usage

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

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

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

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

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 19:40 GMT
  • Updated: Wed, 23 Aug 2023 21:46 GMT

Incorrect action name in graphical notation example

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

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

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

Flows compartment missing in Representative Notation Table

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

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

    An example should be added.

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 14:55 GMT
  • Updated: Wed, 23 Aug 2023 21:38 GMT

Flows Compartment example graphical notation missing

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

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

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

Confusing naming in Individual Occurrence example

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

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

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

Incomplete example "Individual Occurrence"

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

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

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:17 GMT
  • Updated: Wed, 23 Aug 2023 21:27 GMT

Examples requirement derivation, cause effect, and refinement missing

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

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 22:13 GMT
  • Updated: Wed, 23 Aug 2023 21:20 GMT

Loop examples incomplete in representative notation table

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

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 22:04 GMT
  • Updated: Wed, 23 Aug 2023 21:20 GMT

Representative notation table uses deprecated «equal»

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

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 12:33 GMT
  • Updated: Wed, 23 Aug 2023 21:19 GMT

Missing graphical notation for n-ary connection def and usage

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

    The representative notation tables in 7.13.1 Connections Overview, and 7.20.1 Requirements Overview, is missing BNF for n-ary connection def and connection usage. Must be fixed in 8.2.3.13.

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 12:19 GMT
  • Updated: Wed, 23 Aug 2023 21:17 GMT

Specification of standard geometric view missing

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 21:00 GMT
  • Updated: Wed, 23 Aug 2023 21:12 GMT

Identify impact views on model organization

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 11:55 GMT
  • Updated: Wed, 23 Aug 2023 21:10 GMT

Textual and graphical notations for flow on connection unclear

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:19 GMT
  • Updated: Wed, 23 Aug 2023 21:07 GMT

Incorrect font in descriptions of AttributeUsage and TransitionUsage

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 20:01 GMT
  • Updated: Tue, 22 Aug 2023 15:35 GMT

CommentAnnotation_Mapping shall be a "unique" mapping

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

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

  • Reported: SysML 2.0a1 — Sun, 20 Aug 2023 15:12 GMT
  • Updated: Sun, 20 Aug 2023 17:27 GMT

Mapping of ActivityEdge does not consider ActivityParameterNodes

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

    The SysML v1 to v2 transformation does not map ActivityParameterNode, but only the references Parameter. The mapping of ActivityEdge must map the ends of the edge, which are connected to an ActivityParameterNode to the target element of the mapping of the Parameter.

  • Reported: SysML 2.0b1 — Sun, 16 Jul 2023 10:57 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

UntypedPin_Mapping redefines operation without any changes

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

    UntypedPin_Mapping (SYSML2-171 renamed it to Pin_Mapping) redefines ownedRelationship(), but does not change anything. Remove the redefined operation.

  • Reported: SysML 2.0a1 — Sun, 2 Jul 2023 06:30 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

UML4SysML::Activities and StateMachines owned by blocks should be mapped to definition elements

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

    Activities owned by blocks are mapped to ActionUsage, but should be ActionDefinition. Same for StateMachines

  • Reported: SysML 2.0a1 — Thu, 8 Jun 2023 19:02 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

Map OpqueBehavior always to ActionDefinition

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

    OpaqueBehavior not owned by a package is mapped to a ActionUsage. Since a UML4SysML::OpaqueBehavior is also a type it should be mapped to a conforming element in SysML v2, i.e., only to ActiobDefinition.

  • Reported: SysML 2.0a1 — Mon, 3 Jul 2023 15:45 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

Mapping of allcation between usage and definition or definition and usage elements does not work

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

    The mapping of the allocation relationship only considers allocations from definition to definition and usage to usage elements, but not a mixed allocation.

  • Reported: SysML 2.0a1 — Thu, 29 Jun 2023 06:09 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

Typo in AEAReceiverFeatureValue_Mapping::value()

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

    ACAReceiverFeatureReferenceExpression_Mapping should be AEAReceiverFeatureReferenceExpression_Mapping

  • Reported: SysML 2.0a1 — Mon, 26 Jun 2023 07:16 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

CreateLinkObjectAction_Mapping should specialize CreateLinkAction_Mapping

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

    The UML4SysML::CreateLinkObjectAction is a specialization of UML4SysML::CreateLinkAction. Accordingly, the CreateLinkObjectAction_Mapping should specialize CreateLinkAction_Mapping.

  • Reported: SysML 2.0a1 — Mon, 26 Jun 2023 06:31 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

AEAParameterMembership_Mapping::ownedMemberParameter cannot return OclUndefined

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

    The ownedMemberParameter must return an element and not OclUndefined. The case where the if-statement leads to OclUndefined must be checked before AEAParameterMembership_Mapping::ownedMemberParameter is called.

  • Reported: SysML 2.0a1 — Mon, 26 Jun 2023 05:41 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

RVVAVariable_Mapping uses CommonAssignmentActionOwningMembership_Mapping, but should be a factory class

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

    RVVAVariable_Mapping uses CommonAssignmentActionOwningMembership_Mapping, but it should be the factory class AssignmentActionUsageOwningMembership_Factory.

    The resolution SYSML2-4 changed CommonAssignmentActionOwningMembership_Mapping to AssignmentActionUsageOwningMembership_Factory, but oversaw the usages of the mapping class in RVVAVariable_Mapping.

  • Reported: SysML 2.0a1 — Sun, 25 Jun 2023 13:03 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

TestCaseVerifyRequirementUsage_Mapping uses non-existing mapping classes

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

    TestCaseVerifyRequirementUsage_Mapping ::ownedRelationships() uses the mapping classes CaseSubjectMembership_Mapping, which do not exist.

    It existed in a previous version but was removed without updating TestCaseVerifyRequirementUsage_Mapping .

  • Reported: SysML 2.0a1 — Sat, 24 Jun 2023 11:59 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

TestCaseActivity_Mapping uses non-existing mapping classes

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

    TestCaseActivity_Mapping::ownedRelationships() uses the mapping classes CaseSubjectMembership_Mapping and CaseObjectiveMembership_Mapping, which do not exist.

    They existed in a previous version but were removed without updating TestCaseActivity_Mapping.

  • Reported: SysML 2.0a1 — Sat, 24 Jun 2023 09:42 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

ObjectFlows targeting a final node or a activity parameter node cannot be mapped

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

    All target nodes of object flows are handled the same, but activity final nodes are not covered yet, flow final nodes are mapped to a library element, and activity parameter nodes are ignored by the transformation and replaced by the parameter. The object flow mapping must consider the handling of these cases.

  • Reported: SysML 2.0a1 — Thu, 22 Jun 2023 16:13 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

Resolution of approved issue SYSML2-23 uses outdated mapping classes

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

    The resolution forgot to update two usages of the mapping class ObjectFlowItemFlowEndRedefinition_Mapping which is now a factory ObjectFlowItemFlowEndRedefinition_Factory class.

    The error is in the OCL code of ObjectFlowItemFlowEndReferenceUsage_Mapping::ownedRelationships().

  • Reported: SysML 2.0a1 — Thu, 22 Jun 2023 12:48 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

RSFAReferenceUsageFeatureMembership_Mapping uses non-existing mapping class

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

    RSFAReferenceUsageFeatureMembership_Mapping uses the non-existing mapping class ReadStructuralFeatureActionReferenceUsage_Mapping, but it should be RSFAReferenceUsage_Mapping

  • Reported: SysML 2.0a1 — Thu, 22 Jun 2023 01:24 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

ControlFlowSuccessionAsUsage_Mapping uses non-existing mapping class

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

    ownedRelationship() calls the mapping class ControlFlowFinalNodeTargetEndFeatureMembership_Mapping, but it does exist. Instead it should be ControlFlowFinalNodeFeatureMembership_Mapping.

  • Reported: SysML 2.0a1 — Wed, 21 Jun 2023 18:30 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

TIAOperatorExpression_Mapping uses non-existing mapping class EqualOperatorExpressionOperand_Mapping

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

    The operation TIAOperatorExpression_Mapping::ownedRelationship() uses mapping class EqualOperatorExpressionOperand_Mapping, but it does not exist.

  • Reported: SysML 2.0a1 — Wed, 21 Jun 2023 20:38 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

Helpers::activityOwnedRelationships mixes up FinalNodes and FlowFinalNodes

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

    The Helper operation activityOwnedRelationships calls the mapping class FlowFinalNode_Mapping with a set of final nodes including activity final nodes, but should only be final nodes.

    Activity final nodes are currently excluded from the transformation (see SYSML2-106).

  • Reported: SysML 2.0a1 — Wed, 21 Jun 2023 17:53 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

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

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

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

  • Reported: SysML 2.0a1 — Wed, 17 May 2023 17:53 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

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

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

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

  • Reported: SysML 2.0a1 — Wed, 3 May 2023 05:35 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

Mapping of SysMLv1::ItemFlow does not consider the itemProperty

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

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

  • Reported: SysML 2.0a1 — Wed, 3 May 2023 12:48 GMT
  • Updated: Tue, 15 Aug 2023 00:22 GMT

Sample::calculation has an incorrect type

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

    In 9.4.3.2.5 Sample (in the Sampled Function model in the Analysis Domain LIbrary), the feature calculation has type CalculationUsage. However, in the actual library model, calculation is a CalculationUsage, which means it should have the base library definition Calculation as its type, not the abstract syntax element CalculationUsage

  • Reported: SysML 2.0b1 — Thu, 10 Aug 2023 02:35 GMT
  • Updated: Thu, 10 Aug 2023 02:35 GMT

Wrong imported package notation

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

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

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:57 GMT
  • Updated: Tue, 8 Aug 2023 21:17 GMT

Representative example "Package with members" to be improved

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

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

  • Reported: SysML 2.0b1 — Thu, 3 Aug 2023 20:39 GMT
  • Updated: Tue, 8 Aug 2023 21:02 GMT

Incomplete textual notation in example "Variants Compartment"

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

    In example "Variants Compartment" textual notation should include part def PartDef1, and item def ItemDef1, and also part1 : PartDef1 and item1 : ItemDef1.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:13 GMT
  • Updated: Tue, 8 Aug 2023 09:50 GMT

Incomplete textual notation in example "Subsetting"

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

    Example "Subsetting" is missing specification of the perform action action1 : Action1 that is shown as inherited in the graphical notation. Add part def Part1 in textual notation from preceding example "Usage Definition".

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:12 GMT
  • Updated: Mon, 7 Aug 2023 22:15 GMT

Missing graphical notation allocating flow to connection

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

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

    This should be added.

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 11:58 GMT
  • Updated: Thu, 3 Aug 2023 11:56 GMT

Feature modifiers missing in Portion Membership examples

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

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

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 15:37 GMT
  • Updated: Wed, 2 Aug 2023 17:58 GMT

Feature modefiers missing in Feature Membership examples

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

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

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 15:35 GMT
  • Updated: Wed, 2 Aug 2023 17:57 GMT

Incomplete flow notation in example "Flow as Node"

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

    In example "Flow as Node" check whether flow from source :> action1.item1 should be reference subsetting? Add keyword from to the nested flows.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:43 GMT
  • Updated: Wed, 2 Aug 2023 17:56 GMT

Incorrect item flow notation in example "Interface as Node"

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

    In example "Interface as Node" remove arrow heads from the nested connections, and move arrow head between pa and pb to end of line, add message of item1:Item1 from pa to pb to the interface2 usage in the textual notation. Also add open curly bracket directly after interface2, and closing curly bracket after the ellipsis.

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:42 GMT
  • Updated: Wed, 2 Aug 2023 17:55 GMT

Representative notation for filtered package import missing

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

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

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 13:10 GMT
  • Updated: Wed, 2 Aug 2023 17:37 GMT

Package import wildcard is missing

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

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

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:58 GMT
  • Updated: Wed, 2 Aug 2023 17:35 GMT

Missing representative notation for causation and requirements derivation

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

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

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:33 GMT
  • Updated: Wed, 2 Aug 2023 17:29 GMT

Nesting parameter symbol is missing optional nested parameter

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

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

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:30 GMT
  • Updated: Wed, 2 Aug 2023 17:26 GMT

Binding between action parameters and directed features on ports missing

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

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

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:14 GMT
  • Updated: Wed, 2 Aug 2023 17:23 GMT

Adornments on ends missing in graphical syntax

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

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

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:12 GMT
  • Updated: Wed, 2 Aug 2023 17:17 GMT

Metadata declaration needs clarification

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

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

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:11 GMT
  • Updated: Wed, 2 Aug 2023 16:49 GMT

Symbol for metadata def is missing

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

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

  • Reported: SysML 2.0b1 — Wed, 2 Aug 2023 12:09 GMT
  • Updated: Wed, 2 Aug 2023 16:39 GMT

Mapping of ObjectFlows with ForkNodes

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

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

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

  • Reported: SysML 2.0b1 — Mon, 24 Jul 2023 13:16 GMT
  • Updated: Mon, 24 Jul 2023 14:48 GMT

Mapping of ObjectFlows with DecisionNodes

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

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

  • Reported: SysML 2.0b1 — Mon, 24 Jul 2023 14:47 GMT
  • Updated: Mon, 24 Jul 2023 14:48 GMT

Mapping of ObjectFlows with JoinNodes

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

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

  • Reported: SysML 2.0b1 — Mon, 24 Jul 2023 14:30 GMT
  • Updated: Mon, 24 Jul 2023 14:31 GMT

Case View is not a standard view

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

    The Case View that is listed in the first table in clause 9.2.19.1 and defined in clause 9.2.19.2.3 is not one of the standard views and should be removed.
    Note: The intent is to respecify the Case View as a specialization of the (standard) General View with a suitable filter.

  • Reported: SysML 2.0a1 — Wed, 12 Jul 2023 14:28 GMT
  • Updated: Mon, 24 Jul 2023 00:07 GMT

Error in textual BNF for MessageDeclaration

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

    The textual BNF production for MessageDeclaration includes a reference to ItemFeatureMember, which does not exist. This reference should instead be to FlowPayloadFeatureMember.

  • Reported: SysML 2.0a1 — Tue, 27 Jun 2023 17:14 GMT
  • Updated: Mon, 24 Jul 2023 00:07 GMT

Error in textual BNF for TargetSuccession

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

    The textual BNF production for the TargetSuccession is missing the keyword then.

  • Reported: SysML 2.0a1 — Thu, 29 Jun 2023 14:36 GMT
  • Updated: Mon, 24 Jul 2023 00:07 GMT

Graphical BNF opaque "text block" productions

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

    In the graphical BNF there is a set of textual productions related to compartments that are currently mapped to a "text block" placeholder. They need to be replaced with concrete textual productions.

    1. In 8.2.3.24, production use-cases-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: use-cases-compartment-contents = (use-cases-compartment-element)* '…'? and use-cases-compartment-element = el-prefix? OccurrenceUsagePrefix CalculationUsageDeclaration CaseBody '…'
    2. In 8.2.3.5, production packages-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: packages-compartment-contents = (packages-compartment-element)* '…'? and packages-compartment-element = el-prefix? TBD
    3. In 8.2.3.5, production members-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: members-compartment-contents = (members-compartment-element)* '…'? and members-compartment-element = el-prefix? TBD
    4. In 8.2.3.5, production relationships-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: relationships-compartment-contents = (relationships-compartment-element)* '…'? and relationships-compartment-element = el-prefix? TBD
    5. In 8.2.3.6, production variants-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: variants-compartment-contents = (variants-compartment-element)* '…'? and variants-compartment-element = el-prefix? TBD
    6. In 8.2.3.6, production variant-elementusages-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: variant-elementusages-compartment-contents = (variant-elementusages-compartment-element)* '…'? and variant-elementusages-compartment-element = el-prefix? TBD
    7. In 8.2.3.16, production performed-by-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: performed-by-compartment-contents = (performed-by-compartment-element)* '…'? and performed-by-compartment-element = el-prefix? TBD
    8. In 8.2.3.17, production succession-compartment-contents incorrectly equates to text-block placeholder. It should be renamed to successions-compartment-contents, and it should be replaced with two productions: successions-compartment-contents = (successions-compartment-element)* '…'? and successions-compartment-element = el-prefix? TBD
    9. In 8.2.3.18, production calcs-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: calcs-compartment-contents = (calcs-compartment-element)* '…'? and calcs-compartment-element = el-prefix? TBD
    10. In 8.2.3.18, production result-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: result-compartment-contents = result-compartment-element? and result-compartment-element = el-prefix? TBD
    11. In 8.2.3.20, production require-constraints-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: require-constraints-compartment-contents = (require-constraints-compartment-element)* '…'? and require-constraints-compartment-element = el-prefix? TBD
    12. In 8.2.3.20, production assume-constraints-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: assume-constraints-compartment-contents = (assume-constraints-compartment-element)* '…'? and assume-constraints-compartment-element = el-prefix? TBD
    13. In 8.2.3.20, production satisfies-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: satisfies-compartment-contents = (satisfies-compartment-element)* '…'? and satisfies-compartment-element = el-prefix? TBD
    14. In 8.2.3.25, production exposes-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: exposes-compartment-contents = (exposes-compartment-element)* '…'? and exposes-compartment-element = el-prefix? TBD
    15. In 8.2.3.25, production rendering-compartment-contents incorrectly equates to text-block placeholder. It should be replaced with two productions: rendering-compartment-contents = (rendering-compartment-element)* '…'? and rendering-compartment-element = el-prefix? TBD
  • Reported: SysML 2.0a1 — Mon, 26 Jun 2023 17:07 GMT
  • Updated: Mon, 24 Jul 2023 00:07 GMT

Number missing from table listing Standard View Definitions

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

    The first table in clause 9.2.19.1 that lists the Standard View Definitions does not have a number nor a caption. Table number 38 and caption should be added.

  • Reported: SysML 2.0a1 — Wed, 14 Jun 2023 10:29 GMT
  • Updated: Mon, 24 Jul 2023 00:07 GMT

Table 38 "Standard View Definitions" redundant

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

    Remove existing Table 38 "Standard View Definitions", as well as the immediately preceding paragraph, from subclause 9.2.19.1, since this information is redundant and potentially inconsistent with the graphical BNF in subclause 8.2.3.

  • Reported: SysML 2.0a1 — Wed, 14 Jun 2023 10:23 GMT
  • Updated: Mon, 24 Jul 2023 00:07 GMT

Limitation on specifying view renderings

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

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

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

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

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 19:51 GMT
  • Updated: Mon, 24 Jul 2023 00:07 GMT

Connection declaration does not allow a feature value

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

    The second line of the following does not parse:

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

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

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

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

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

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

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

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

Graphical BNF for n-ary connections missing


Various incorrect Graphical BNF productions

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

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

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

    1. In 8.2.3.9, production occurrences-compartment-element incorrectly uses DefinitionBodyItem. DefinitionBodyItem should be removed.
    2. In 8.2.3.10, production items-compartment-element incorrectly uses DefinitionBodyItem. DefinitionBodyItem should be removed.
    3. In 8.2.3.11, production parts-compartment-element incorrectly uses OccurrenceUsagePrefix UsageDeclaration. It should be OccurrenceUsagePrefix Usage.
    4. In 8.2.3.12, production ports-compartment-element incorrectly uses OccurrenceUsagePrefix UsageDeclaration. It should be OccurrenceUsagePrefix Usage.
    5. In 8.2.3.13, production connections-compartment-element incorrectly uses OccurrenceUsagePrefix UsageDeclaration ConnectorPart+ DefinitionBodyItem*. It should be OccurrenceUsagePrefix UsageDeclaration ( 'connect' ConnectorPart )? | 'connect' ConnectorPart ) UsageBody.
    6. In 8.2.3.14, production interfaces-compartment-element incorrectly uses InterfaceUsageDeclaration InterfaceBodyDefinition*. It should be OccurrenceUsagePrefix InterfaceUsageDeclaration InterfaceBody.
    7. In 8.2.3.16, production actions-compartment-element incorrectly uses OccurrenceUsagePrefix ActionUsageDeclaration ActionBodyItem*. It should be OccurrenceUsagePrefix ActionUsageDeclaration.
    8. In 8.2.3.16, production perform-actions-compartment-element incorrectly uses PerformActionUsageDeclaration ActionBodyItem*. It should be OccurrenceUsagePrefix PerformActionUsageDeclaration.
    9. In 8.2.3.17, production states-compartment-element incorrectly uses UsageDeclaration. It should be OccurrenceUsagePrefix ActionUsageDeclaration.
  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 13:17 GMT
  • Updated: Mon, 24 Jul 2023 00:07 GMT

Incorrect production for attributes-compartment-element

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

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

    It should reference "UsagePrefix Usage".

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 13:15 GMT
  • Updated: Mon, 24 Jul 2023 00:07 GMT

Graphical BNF flow-label and interface-label productions missing

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:52 GMT
  • Updated: Mon, 24 Jul 2023 00:07 GMT

Graphical BNF sq-message-label usage incorrect

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:50 GMT
  • Updated: Mon, 24 Jul 2023 00:07 GMT

Graphical BNF interconnection view production incorrect

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

    interconnection view production missing interfaces

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:51 GMT
  • Updated: Mon, 24 Jul 2023 00:07 GMT

Graphical BNF sq-message reference incorrect

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

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

    Resolution:
    Change the production rule

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:49 GMT
  • Updated: Mon, 24 Jul 2023 00:07 GMT
  • Attachments:

Textual production for sq-proxy-label incorrect

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:48 GMT
  • Updated: Mon, 24 Jul 2023 00:07 GMT

Graphical BNF production sq-part refers to wrong port

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:25 GMT
  • Updated: Mon, 24 Jul 2023 00:07 GMT
  • Attachments:

Transformation does not cover the mapping of Unit and QuantityKind

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

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

  • Reported: SysML 2.0b1 — Thu, 20 Jul 2023 15:04 GMT
  • Updated: Fri, 21 Jul 2023 14:24 GMT
  • Attachments:

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

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

    The transformation does not map the Parameter::isStreaming.

  • Reported: SysML 2.0b1 — Tue, 18 Jul 2023 17:12 GMT
  • Updated: Thu, 20 Jul 2023 15:04 GMT

Message and flow connection ends should be occurrence usages

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

    The end features of MessageConnection, FlowConnection and SuccessionFlowConnection in the standard library package Connections are typed as Occurrences, but they are currently syntactically reference usages, not occurrence usages. However, the abstract syntax for EventOccurrenceUsage requires that its referenced eventOccurrence must actually be an OccurrenceUsage. This means that the source and target ends of, e.g., a message, if inherited from MessageConnection and not redefined, cannot be referenced by EventOccurrenceUsages, which prevents an intended use in "sequence diagram" modeling.

  • Reported: SysML 2.0b1 — Sun, 16 Jul 2023 20:35 GMT
  • Updated: Sun, 16 Jul 2023 20:35 GMT

Conform as a Generalization is Incorrect - A View is Not a Viewpoint / 'is a' Does Not Equate to Conform

  • Status: open  
  • Source: Eclectica Systems Ltd ( Nic Plum)
  • Summary:

    A Conform relationship is a generalization between a view and a viewpoint.

    This is semantically incorrect. Assuming that viewpoint is being used in ISO 42010 sense (no stated anywhere within the specification so this is an error if true as the common use of 'viewpoint' is not the same as that in the standard) - a viewpoint is a specification against which a view is prepared (and interpreted). A view is not a viewpoint. What's has effectively been said is that a design that conforms to a requirement document is a requirement document.

    In the reverse sense if I want to define that an oak (tree) is an oak I wouldn't then state an Oak (tree) conforms to a Tree.

    If you need to state the conformance relationship between view and viewpoint SysML provides somewhere a 'satisfy' stereotype.

    The history of the OMG misrepresenting or misunderstanding what a 42010::viewpoint is in their documents over the years is woeful.

  • Reported: SysML 1.5 — Sun, 4 Jun 2023 09:16 GMT
  • Updated: Fri, 14 Jul 2023 20:07 GMT

View is not a Viewpoint

  • Status: open  
  • Source: Eclectica Systems Ltd ( Nic Plum)
  • Summary:

    The View conform Viewpoint relationship is shown as a Generalization. This then states that a View is a Viewpoint which is incorrect. A Viewpoint in ISO/IEC/IEEE 42010 terms is a specification against which a View is prepared and interpreted.

    I suspect that this is another example of a long held error where View was described as an instance of a Viewpoint. It isn’t. This has never been true in the international standard.

  • Reported: SysML 1.5 — Tue, 20 Jun 2023 11:15 GMT
  • Updated: Fri, 14 Jul 2023 20:07 GMT

Artifacts and «document»

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

    the statement from v. 1.5 (section A.2)

    SysML provides the capability to represent a document using the UML 2 standard stereotype «document» applied to the artifact model element. Properties of the artifact can capture information about the document. Use a «trace» abstraction to relate the document to model elements. The document can represent text that is contained in the related model elements.

    was removed from 1.6... but 1.6 retained Artifact in its UML4SYSML set...

    I think, either remove Artifact or put the statement back in

  • Reported: SysML 1.6 — Thu, 4 Nov 2021 16:13 GMT
  • Updated: Fri, 14 Jul 2023 19:59 GMT

UML::Artifact is Excluded But Specification Doesn't State With What Documents/Artifacts Are to Be Represented with Instead

  • Status: open   Implementation work Blocked
  • Source: Eclectica Systems Ltd ( Nic Plum)
  • Summary:

    In Table 4.2 UML::Artifact is defined as excluded.

    In previous versions there was a paragraph Figure A.4 - 'SysML provides the capability to represent a document using the UML 2 standard stereotype «document» applied to the artifact model element. '

    This, whilst contradicting the exclusion of Artifact from SysML did at least define how artifacts/documents were to be represented. Now there is absolutely nothing other than we can't use Artifact.

    How are we supposed to represent a document? As there are few to no specialisation hierarchies in the specification it's almost impossible to see the thinking and, say, where / how deployedDocument fits into a taxonomy.

    I'm trying to create a SysML profile and I need to represent a Document, Standard, Contract etc - all artifacts in the UML sense but no idea what I should now be using in a SysML profile.

  • Reported: SysML 1.7b1 — Sat, 24 Jun 2023 11:11 GMT
  • Updated: Fri, 14 Jul 2023 19:56 GMT

SysML Libraries' elements shall have an elementId defined

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

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

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

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

    Linked to a similar issue raised on KerML

  • Reported: SysML 2.0a1 — Thu, 13 Jul 2023 06:51 GMT
  • Updated: Thu, 13 Jul 2023 06:53 GMT

Causation end features need to redefine source and target

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

    The connection definition Causation in the CausationConnections library package has two ends that redefine the non-end features causes and effects from Multicausation.

    However, in the normative CausationConnections.sysml file from the Cause and Effect Domain Library project, these ends are declarated to only subset the source and target ends inherited from BinaryConnection. As a result, the connection definition ends up having four ends rather than two, which is incorrect. Its ends need to redefine source and target, rather than just subsetting them.

    In subclause 9.5.2.2.1 of the specification document, on the other hand, Causation is not shown as specializing BinaryLink at all, and the ends are shown as only redefining the non-end features from Multicausation.

  • Reported: SysML 2.0a1 — Wed, 12 Jul 2023 21:50 GMT
  • Updated: Wed, 12 Jul 2023 21:50 GMT

Some Standard View Definitions should be filtered specializations of General View

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

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

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

  • Reported: SysML 2.0a1 — Wed, 14 Jun 2023 10:44 GMT
  • Updated: Wed, 12 Jul 2023 20:59 GMT

Source and target on binary ConnectionDefinition symbol missing

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 12:57 GMT
  • Updated: Tue, 11 Jul 2023 16:03 GMT

ElementMain_Mapping::ownedRelationship is wrong

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

    ElementMain_Mapping::ownedRelationship deals with owned comments and tries to create an ownership relationship thanks to ElementOwnership_Mapping.
    Instead, this is an Annotation relationship that shall be used here. We can get it thanks to the CommentAnnotation_Mapping.

    However, CommentAnnotation_Mapping misses the computation of ownedRelatedElement that is left to its default value, meaning that the ownership of a comment is never set.

  • Reported: SysML 2.0a1 — Sun, 2 Jul 2023 06:46 GMT
  • Updated: Tue, 4 Jul 2023 20:23 GMT

the getMapped operation cannot be called on ElementOwnership_Mapping

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

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

  • Reported: SysML 2.0a1 — Tue, 4 Jul 2023 20:16 GMT
  • Updated: Tue, 4 Jul 2023 20:23 GMT

Transformation does not cover UML4SysML::FunctionBehavior

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

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

  • Reported: SysML 2.0a1 — Tue, 4 Jul 2023 10:30 GMT
  • Updated: Tue, 4 Jul 2023 10:30 GMT

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

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

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

  • Reported: SysML 2.0a1 — Mon, 3 Jul 2023 16:34 GMT
  • Updated: Mon, 3 Jul 2023 16:34 GMT

Transformation does not cover UML4SysML::DestroyLinkAction

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

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

  • Reported: SysML 2.0a1 — Fri, 30 Jun 2023 18:59 GMT
  • Updated: Fri, 30 Jun 2023 18:59 GMT

Transformation does not cover UML4SysML::CreateLinkAction

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

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

  • Reported: SysML 2.0a1 — Fri, 30 Jun 2023 18:58 GMT
  • Updated: Fri, 30 Jun 2023 18:58 GMT

Transformation does not cover UML4SysML::ReadLinkAction

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

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

  • Reported: SysML 2.0a1 — Fri, 30 Jun 2023 18:56 GMT
  • Updated: Fri, 30 Jun 2023 18:56 GMT

Transformation does not cover UML4SysML::SignalEvent

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

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

  • Reported: SysML 2.0a1 — Fri, 30 Jun 2023 18:53 GMT
  • Updated: Fri, 30 Jun 2023 18:54 GMT

Graphical BNF defines lifeline elements incorrectly

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 14:58 GMT
  • Updated: Mon, 26 Jun 2023 15:29 GMT

Graphical BNF production proxy refers to wrong label

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:40 GMT
  • Updated: Mon, 26 Jun 2023 15:25 GMT

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

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 12:28 GMT
  • Updated: Mon, 26 Jun 2023 15:25 GMT

Subsections of section 7.7.2.3.7 should be ordered alphabetically

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

    The subsections of section 7.7.2.3.7 should be ordered alphabetically.

  • Reported: SysML 2.0a1 — Tue, 20 Jun 2023 18:30 GMT
  • Updated: Tue, 20 Jun 2023 18:31 GMT

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

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

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

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 21:53 GMT
  • Updated: Tue, 20 Jun 2023 04:56 GMT

Redefining feature information missing from specification document

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

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 19:33 GMT
  • Updated: Tue, 20 Jun 2023 04:55 GMT

Universal features can have many values

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

    Clause 9.8.8.2.13 (universalClock), Description, says

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

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

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

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

    and 9.7.2.2.5 (SpatialItem) says its localClock is

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

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

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

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

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

  • Reported: SysML 2.0a1 — Wed, 3 May 2023 15:13 GMT
  • Updated: Tue, 20 Jun 2023 04:54 GMT

Some package-level features are mandatory

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

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

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

    Might be others.

  • Reported: SysML 2.0a1 — Wed, 3 May 2023 15:17 GMT
  • Updated: Tue, 20 Jun 2023 04:53 GMT

ISQ in specification and libraries not aligned

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

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

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

    Might be others.

  • Reported: SysML 2.0a1 — Wed, 3 May 2023 15:29 GMT
  • Updated: Tue, 20 Jun 2023 04:52 GMT

ConstraintBlock mapping parameters to input attributes

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

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

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

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

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

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

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

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

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

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

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

  • Reported: SysML 2.0a1 — Thu, 4 May 2023 15:26 GMT
  • Updated: Tue, 20 Jun 2023 04:52 GMT

Assignment action usages do not specify when their expressions are evaluated

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

    Clause 8.3.16.5 (AssignmentActionUsage), Description, says:

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

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

  • Reported: SysML 2.0a1 — Tue, 2 May 2023 20:38 GMT
  • Updated: Tue, 20 Jun 2023 04:50 GMT

Risk, Source and Verification Method Are Attributes of Any / All Requirements Not Just an Extended Requirement

  • Status: open  
  • Source: Eclectica Systems Ltd ( Nic Plum)
  • Summary:

    The verifyMethod, source and risk attributes are only available for extended requirements i.e. a straight vanilla Requirement has no associated verification method or risk. This doesn't reflect reality / the actual taxonomy and has nothing to do with the sub-classification of a requirement as physical, functional etc. i.e. these are attributes of the parent Requirement not the child extended requirement. It also then requires that a SE has to subclassify before they can ascribe a risk level or verification method.

    Even looking at the definiton of extendedRequirements this definition has nothing to do differentiation in terms of an ontology - only the means to do things. 'A mix-in stereotype that contains generally useful attributes for requirements'

    It also means that if the SE has a requirement that doesn't fit into the OMG classification schema i.e. none of the existing categories then they cannot easily assign these attributes (e.g. a requirement to conform to a standard isn't a design constraint, isn't functional etc). These common attributes should be present without forcing the SE to subclassify before they are available.

  • Reported: SysML 1.5 — Fri, 26 May 2023 11:10 GMT
  • Updated: Thu, 15 Jun 2023 12:48 GMT

Incorrect reference to SysML v1 to SysML v2 Transformation

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

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

  • Reported: SysML 2.0a1 — Wed, 14 Jun 2023 22:00 GMT
  • Updated: Wed, 14 Jun 2023 22:00 GMT

Consider production for standard case view vs filtered general view

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 20:54 GMT
  • Updated: Wed, 14 Jun 2023 10:54 GMT

Typo in section 7.6.3 and section 7.6.4: mappingsto

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

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

  • Reported: SysML 2.0a1 — Mon, 22 May 2023 15:50 GMT
  • Updated: Tue, 13 Jun 2023 01:23 GMT

ControlFlow transformation target ends are not defined correctly

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

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

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

ControlFlow target SuccessionAsUsage should have end feature with reference subsetting

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

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

  • Reported: SysML 2.0a1 — Thu, 11 May 2023 06:48 GMT
  • Updated: Tue, 13 Jun 2023 01:23 GMT

A ConnectionUsage should be owned by a FeatureMembership relationship

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

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

  • Reported: SysML 2.0a1 — Thu, 18 May 2023 06:33 GMT
  • Updated: Tue, 13 Jun 2023 01:23 GMT

Filter for mapping class Behavior_Mapping is useless

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

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

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

Mapping of SysMLv1::ItemFlow does not consider the itemProperty

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

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

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

Introduce GenericToTransitionUsage_Mapping class

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

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

  • Reported: SysML 2.0a1 — Mon, 22 May 2023 15:22 GMT
  • Updated: Tue, 13 Jun 2023 01:23 GMT

GenericToEndFeatureMembership_Mapping::to property redefines itself

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

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

  • Reported: SysML 2.0a1 — Thu, 11 May 2023 06:16 GMT
  • Updated: Tue, 13 Jun 2023 01:23 GMT

Description of Subsetting mapping classes is not correct

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

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

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

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

  • Reported: SysML 2.0a1 — Mon, 15 May 2023 15:53 GMT
  • Updated: Tue, 13 Jun 2023 01:23 GMT

ClassifierBehaviorFeatureMembership_Mapping does not exist

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

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

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

  • Reported: SysML 2.0a1 — Wed, 3 May 2023 04:54 GMT
  • Updated: Tue, 13 Jun 2023 01:23 GMT

EmptyReturnParameterFeatureMembership_Mapping does not exist

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

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

    Instead, it should be ReturnParameterFeatureMembership_Factory.

  • Reported: SysML 2.0a1 — Tue, 2 May 2023 17:51 GMT
  • Updated: Tue, 13 Jun 2023 01:23 GMT

ControlFlowSuccessionAsUsage_Mapping uses non existing mapping class ActivityEdgeInitialNodeSourceEndFeatureMembership_Mapping

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

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

  • Reported: SysML 2.0a1 — Mon, 8 May 2023 17:40 GMT
  • Updated: Tue, 13 Jun 2023 01:23 GMT

ControlFlowSuccessionAsUsage_Mapping uses non existing mapping class

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

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

  • Reported: SysML 2.0a1 — Wed, 10 May 2023 15:45 GMT
  • Updated: Tue, 13 Jun 2023 01:23 GMT

Mapping of allocation between usage elements is not specified yet

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

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 11:23 GMT
  • Updated: Tue, 13 Jun 2023 01:23 GMT

Optimize Pin mapping class generalization hierarchy

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

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

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

  • Reported: SysML 2.0a1 — Mon, 1 May 2023 14:02 GMT
  • Updated: Tue, 13 Jun 2023 01:23 GMT

Mapping of ValueSpecificationActions does not work for untyped pins

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

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

  • Reported: SysML 2.0a1 — Mon, 1 May 2023 14:10 GMT
  • Updated: Tue, 13 Jun 2023 01:23 GMT

Subsections for mapping classes in section 7.7.2.3.9 should be ordered alphabetically

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

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

  • Reported: SysML 2.0a1 — Wed, 19 Apr 2023 12:39 GMT
  • Updated: Tue, 13 Jun 2023 01:23 GMT

REAOutputPin_Mapping should specialize OutputPin_Mapping

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

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

  • Reported: SysML 2.0a1 — Thu, 20 Apr 2023 06:39 GMT
  • Updated: Tue, 13 Jun 2023 01:23 GMT

UML4SysML::ClearVariableAction transformation does not include a ReturnParameter

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

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

  • Reported: SysML 2.0a1 — Tue, 18 Apr 2023 20:46 GMT
  • Updated: Tue, 13 Jun 2023 01:23 GMT

Transformation of UML4SysML::AddStructuralFeatureValueAction is not correct

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

Transformation of UML4SysML::AddVariableValueAction is not correct

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

    The transformation of UML4SysML::AddVariableValueAction contains several issues:

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

ItemFlowEnds of ObjectFlow transformation target are not defined correctly

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

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

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

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

  • Reported: SysML 2.0a1 — Sat, 15 Apr 2023 09:08 GMT
  • Updated: Tue, 13 Jun 2023 01:23 GMT

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

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

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

  • Reported: SysML 2.0a1 — Wed, 19 Apr 2023 17:29 GMT
  • Updated: Mon, 12 Jun 2023 08:37 GMT

Transformation of UML4SysML::InterruptibleActivityRegion is not specified yet


Transformation of UML4SysML::ActivityFinalNode is not specified yet

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:04 GMT
  • Updated: Sun, 11 Jun 2023 10:30 GMT

Transformation does not cover SysMLv1::NoBuffer

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 08:03 GMT
  • Updated: Sat, 10 Jun 2023 11:23 GMT

Transformation does not cover SysMLv1::Overwrite

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 08:02 GMT
  • Updated: Sat, 10 Jun 2023 11:23 GMT

Transformation does not cover UML4SysML::ActivityPartition

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:41 GMT
  • Updated: Sat, 10 Jun 2023 11:22 GMT

Transformation does not cover UML4SysML::Extend

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:07 GMT
  • Updated: Sat, 10 Jun 2023 11:21 GMT

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

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 07:01 GMT
  • Updated: Sat, 10 Jun 2023 11:21 GMT

Transformation does not cover UML4SysML::GeneralizationSet

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

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

  • Reported: SysML 2.0a1 — Sat, 29 Apr 2023 06:56 GMT
  • Updated: Sat, 10 Jun 2023 11:19 GMT

Action::decisionTransitions should subset Action::transitions

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

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

  • Reported: SysML 2.0a1 — Sun, 28 May 2023 19:32 GMT
  • Updated: Sun, 28 May 2023 19:32 GMT

Editoral corrections in 7.16.11

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

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 23:04 GMT
  • Updated: Tue, 16 May 2023 00:33 GMT

Errors in textual BNF for RequirementDefinition and ConcernDefinition

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

    In the BNF production for RequirementDefinition in 8.2.2.20.1:

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

    and the BNF production for ConcernDefinition in 8.2.2.20.3:

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

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

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

Error in assert constraint example

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

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

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

Packages can also have compartments

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

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 20:57 GMT
  • Updated: Tue, 16 May 2023 00:33 GMT

Association end name " /usageWithDirectedUsage" has a typo

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 21:08 GMT
  • Updated: Tue, 16 May 2023 00:33 GMT

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

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 19:36 GMT
  • Updated: Tue, 16 May 2023 00:33 GMT

Inefficient graphical notation specification tooling

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

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

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

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

  • Reported: SysML 2.0a1 — Thu, 27 Apr 2023 15:28 GMT
  • Updated: Tue, 16 May 2023 00:33 GMT

Spatial links can be occurrences

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

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

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

    but

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

Standard view filters incomplete

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

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

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

    (Derived from GSWG ID#01).

  • Reported: SysML 2.0a1 — Sun, 23 Apr 2023 17:52 GMT
  • Updated: Tue, 16 May 2023 00:33 GMT

Error in InterfaceUsage semantics subclause

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

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

  • Reported: SysML 2.0a1 — Wed, 26 Apr 2023 22:47 GMT
  • Updated: Tue, 16 May 2023 00:33 GMT

"Elements not mapped" table sections are empty

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

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

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

  • Reported: SysML 2.0a1 — Tue, 11 Apr 2023 06:02 GMT
  • Updated: Tue, 16 May 2023 00:33 GMT

Pin_Mapping::filter: property src should be from

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

    The src property in the filter condition should be from.

  • Reported: SysML 2.0a1 — Sat, 15 Apr 2023 18:03 GMT
  • Updated: Tue, 16 May 2023 00:33 GMT

Standard view filters incomplete

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

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

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

  • Reported: SysML 2.0a1 — Sun, 23 Apr 2023 18:07 GMT
  • Updated: Tue, 16 May 2023 00:33 GMT

UntypedPin_Mapping::filter: property src should be from

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

    The src property in the filter condition should be from.

  • Reported: SysML 2.0a1 — Sat, 15 Apr 2023 17:58 GMT
  • Updated: Tue, 16 May 2023 00:33 GMT

Transformation does not cover the different UML4SysML::PseudoStates

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

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

  • Reported: SysML 2.0a1 — Sat, 6 May 2023 12:22 GMT
  • Updated: Sat, 6 May 2023 12:22 GMT

XMI and JSON for model libraries

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

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

  • Reported: SysML 2.0a1 — Fri, 28 Apr 2023 19:54 GMT
  • Updated: Sat, 29 Apr 2023 20:44 GMT

XMI and JSON for example model

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

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

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

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

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

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

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

Example analysis case fuelEconomyAnalysis

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

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

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

Example FrontAxle definition

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

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

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

Accepters on transition usages from entry actions

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

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

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

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

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

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

Transformation does not cover SysMLv1::AllocateActivitiyPartition

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

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

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

Transformation does not cover SysMLv1::PropertySpecificType

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

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

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

Transformation does not cover SysMLv1::EndPathMultiplicity

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

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

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

Transformation does not cover SysMLv1::ParticipantProperty

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

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

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

Transformation does not cover SysMLv1::BoundReference

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

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

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

Transformation does not cover SysMLv1::DistributedProperty

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

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

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

Transformation does not cover SysMLv1::Expose

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

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

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

Transformation does not cover SysMLv1::Conform

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

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

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

Transformation does not cover SysMLv1::View

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

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

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

Transformation does not cover SysMLv1::InvocationOnNestedPortAction

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

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

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

Transformation does not cover SysMLv1::~InterfaceBlock

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

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

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

Transformation does not cover SysMLv1::FlowProperty

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

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

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

Transformation does not cover SysMLv1::AddFlowPropertyValueOnNestedPortAction

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

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

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

Transformation does not cover SysMLv1::ChangeStructuralFeatureEvent

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

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

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

Transformation does not cover SysMLv1::TriggerOnNestedPort

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

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

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

Transformation does not cover UML4SysML::UnmarshallAction

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

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

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

Transformation does not cover UML4SysML::LinkEndData