Webel's "super-relational" Note pages!

A Note is a short categorised statement, claim, policy, tip, or issue tracker Throughout this site, content is often related to supporting Notes, and each Note page links back to the content pages that reference it! The Note and Snippet concepts are very closely related and they support each other.
Look for "super-relational" Note page links at the bottom of most content pages!
Note kind Note Spec tag UML keywords SysML keywords Keywords
ANTI-PATTERN, ISSUE, WARNING There is no «port» stereotype keyword for Port or Property in UML-2.5.1 or SysML-1.6. It is assumed to be introduced in some SysML and SysPhS specification diagrams as a custom or user-defined stereotype for special illustration purposes. SysPhS-1.1 «keyword», Port, Association, Association::memberEnd, Association::ownedEnd, user defined Stereotype, custom Stereotype "standard" Port, SysPhS specification figure SysPhS
TOOL There is no ElementValue in UML-2.5.1 (although one has been proposed) it is an extension used by the MagicDraw tool family for handling tagged values ValueSpecification, MagicDraw:ElementValue MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
ASSERTION, TIP The «Subsystem» stereotype for UML Components has nothing to do with the non-normative SysML «subsystem» stereotype for Blocks Component, «Subsystem» Block, «subsystem»
POLICY The Webel versions of the SysML HSUV sample problems and specification sample figures use "standard" Ports EXCEPT where ProxyPorts or FullPorts are explicitly indicated in the specification SysML-1.6 Port "standard" Port, FullPort, ProxyPort SysML, Systems Modeling Language
NAMING, VARIATION The Webel trail versions of the Activity Diagrams D.36 and D.38 use the name 'transMode' for the output Parameter and corresponding ActivityParameterNode (consistent with the spec figure D.38) NOT 'transMode_imported' (as in spec figure D.36) Parameter, ActivityParameterNode HSUV sample problem
CONVENTION, MODELLING, NAMING, TIP The Webel recipe for pragramatic SE with SysML omits many of the concerns addressed by fully-fledged systems engineering frameworks. Many of these can be partially addressed by using custom Stereotypes for extraction using query view tables. SysML-1.6, SysML-1.7, SysMLv2, UML-2.5.1 Package, Model, NamedElement::name SysML, Systems Modeling Language, SysMLv1, MBSE, Model-Based Systems Engineering, Webel Best Practice, Webel::SE:«whitebox», Webel::SE:«blackbox», Webel::SE:«design», Webel::SE:pragmatic
MODELLING, TIP, TOOL The Webel recipe for pragramatic SE with SysML adopts the MagicDraw/Cameo tool friendly approach of using a SystemContext as 'subject' of top-level UseCases (although using a System as 'subject' can also be used). UseCase, UseCase::subject SysML, Systems Modeling Language, SysMLv1, MBSE, Model-Based Systems Engineering, Webel Best Practice, Webel::SE:pragmatic, MagicGrid, Cameo Systems Modeler, MagicDraw SysML, CATIA Magic
ASSERTION The Webel Parsing Analysis recipe promotes a clearly scoped modelling workflow. Webel Parsing Analysis, parsing analysis, WPA:«document», WPA:«snippet»
TIP The Webel Parsing Analysis recipe for SysML1.x does not use the ElementGroup directly, it extends it as a user-defined Snippet stereotype with keyword «snippet» and with MagicDraw Customization. Stereotype, custom Stereotype, MD:Customization, user defined Stereotype, Comment ElementGroup Webel Parsing Analysis, WPA:«snippet»
NAMING, POLICY, STYLE The Webel modelling style, naming conventions, and Best Practices for SysML are more consistent than most SysML spec diagrams. When following Webel courses please DO NOT use the spec sample diagrams (which serve a different purpose) as visual references! Webel Best Practice, Webel Parsing Analysis, SysML, Systems Modeling Language
TIP The vendor-specific Action Language Helper (ALH) API can be accessed from all of the various action scripting languages available in MagicDraw, Cameo Systems Modeler, and Cameo Simulation Toolkit Magic Model Analyst [Cameo Simulation Toolkit], MagicDraw SysML, MagicDraw UML, Cameo Systems Modeler, Action Language Helper, ALH
ANTI-PATTERN, MODELLING The use of an additional «port» keyword on a Port is usually redundant and causes clutter. The use of an additional «port» keyword on a basic Property is an obsolete trick. Please don't imitate it even if you see it in some specification sample diagrams! Port, Stereotype, «keyword», custom Stereotype, user defined Stereotype "standard" Port Webel Best Practice, SysML, Systems Modeling Language, UML, Unified Modeling Language
ISSUE, LIMITATION, WARNING The UML «Trace» and SysML Trace can't be applied to a Slot as target (because Slot is just an Element, not a NamedElement). SysML-1.6, SysML-1.7 Trace, «trace», Slot, DirectedRelationship::/source, DirectedRelationship::/target, Dependency::client, Dependency::supplier, Abstraction Trace, Trace::getTracedFrom(in ref) SysML, Systems Modeling Language
TIP The UML multiplicity range notations '0..*' and '*' are completely equivalent UML-2.5.1 multiplicity, MultiplicityElement, MultiplicityElement::/lower, MultiplicityElement::/upper, LiteralUnlimitedNatural, *
DISPLAY, NAMING, WARNING The UML InformationFlow notation and the SysML ItemFlow notation can sometimes clash with the notation of named Associations and named and typed Connectors InformationFlow, InformationFlow::conveyed ItemFlow, ItemFlow::itemProperty
ASSERTION, CAVEAT The UML Artifact and its UML standard profile extensions such as «document» Document and «file» File are NOT included in UML4SysML. Artifact, «document», «file»
ASSERTION, MODELLING, STYLE The targeting of the Modelica and Simulink simulation language families by the SysML Extension for Physical Interaction and Signal Flow Simulation (SysPhS) encourages development of SysML models aligned with known practices for a wide class of problems! SysML-1.6, SysML-1.7, SysPhS-1.1 Modelica, Simulink, Simscape, Stateflow, SysML, Systems Modeling Language, physical interaction, signal flow, Model-Based Systems Engineering, model-based development, model
ISSUE, LIMITATION, WARNING The SysML1.6 derived /tracedTo is only available on AbstractRequirement (but in MagicDraw/Cameo you can use derived relationships to achieve the same thing on other kinds of NamedElement). SysML-1.6, SysML-1.7 Trace, «trace», Property::isDerived Trace, Trace::getTracedFrom(in ref), AbstractRequirement::/tracedTo SysML, Systems Modeling Language, MagicDraw SysML, MD SysML, Cameo Systems Modeler
CAPABILITY, TIP The SysML Trace relationship can be used as a quick way to traceably elicit model elements from an identified diagram or table from a domain source document. You may visually remove the Trace symbols as each element is elicited to reduce clutter. SysML-1.6, SysML-1.7 Trace, «trace» Trace, Trace::getTracedFrom(in ref) SysML, Systems Modeling Language, Webel Parsing Analysis
ASSERTION The SysML specification refers to 'part property' as a concept (as a type of block property) but there is no stereotype PartProperty; MagicDraw/Cameo as an additional stereotype PartProperty to encapsulate the concept SysML-1.6 part part property
ASSERTION, TIP The SysML Parametric Diagram and the ContraintBlock technology for equations and mathematics is clever, powerful, useful, and integrates well with the other model-based engineering aspects of SysML. Constraint ConstraintBlock, constraint parameter mathematics, equation
ASSERTION The SysML non-normative extended requirements are NOT offered as the ultimate set of requirements categories or requirements fields, but they are highly usable and can be easily adapted. SysML-1.6 AbstractRequirement, Requirement, ExtendedRequirement, VerificationMethodKind, RiskKind, «extendedRequirement», «functionalRequirement», «interfaceRequirement», «performanceRequirement», «physicalRequirement», «designConstraint»
ASSERTION The SysML InterfaceBlock can be used for general contracts (it is NOT just for use as the Type of a ProxyPort)! InterfaceBlock design-by-contract, contract
TIP The SysML Copy relationship can be used to "import" Requirements from an existing read-only library into a new project context. Copy, Requirement Systems Modeling Language, systems engineering, Model-Based Systems Engineering
CAVEAT The SysML Complex "primitive" ValueType does in fact have substructure: realPart:Real and imaginaryPart:Real SysML-1.6 PrimitiveValueType, Complex, ValueType
ASSERTION, NAMING, WARNING The SysML block compartment name 'initialValues' for what are really "context-specific values" is confusing - even completely misleading; please just think of them as 'contextValues' (and initial values as a special context case) SysML-1.6 Parameter::defaultValue, compartment initialValues compartment, contextValues compartment, context-specific values, initial values
CAVEAT The Signal trigger simulator in Cameo Simulation Toolkit 19SP3 does not support run-time user-defined attribute values (but you can define defaults) Trigger, Signal, Classifier::attribute Magic Model Analyst [Cameo Simulation Toolkit]
DISPLAY The ProxyPort «proxy» and FullPort «full» stereotype keywords can quickly lead to clutter in diagrams. The SysML Revision Task Force is working on some new concise notational indicators on the Port rectangle symbol itself. Stereotype, «keyword» ProxyPort, «proxy», FullPort, «full» SysML, Systems Modeling Language
ASSERTION, TIP The OMG SysML language deliberately does not aim to restrict users and tools to one strict systems engineering methodology; it provides flexible capabilities and options for use by many model-based systems engineering methodologies and tools. systems engineering, Model-Based Systems Engineering, requirements engineering, SysML, Systems Modeling Language
CONVENTION, NAMING, POLICY The name of a «testCase» Behavior may be verbose and may use natural language, but should always start with a Capital letter. Behavior, Activity, Interaction, NamedElement, NamedElement::name TestCase, «testCase» Webel Best Practice
WARNING The mechanism for conjugated Ports has been changed in SysML 1.6, it now conjugates the Type! If you are using an InterfaceBlock to type a Port you can conjugate that 'original' on another Port by typing it with an ~InterfaceBlock. SysML-1.6 Port InterfaceBlock, ~InterfaceBlock, conjugation
CAVEAT, ISSUE The markup of Snippet page titles on this CMS web site is sometimes restricted (especially concerning subscripts and superscripts such as used in mathematical and scientific notation). Visit the linked Snippet page for the quote with full markup. Drupal8
CAPABILITY, DISPLAY, TOOL The MagicDraw/Cameo feature "Enable Parts Compartments" really means "Enable SysML Compartments" Port Cameo Systems Modeler, MagicDraw SysML
ISSUE, MODELLING, TIP, TOOL, WARNING, WORKAROUND The integration between Wolfram Workbench and Mathematica is partly gammy (as of latest versions 2022-08-23) Mathematica, Mathematica:notebook, Wolfram, Wolfram Language
TIP The grouping of member elements by an ElementGroup is denoted here "logical" in the sense that it does not "steal ownership" of member elements (as opposed to "physical" ownership of elements in the model) ElementGroup, ElementGroup::/member, ElementGroup::orderedMember logical grouping
ASSERTION The entry, doActivity, and effect Behaviors defined on a submachine State are specific that particular usage of its Submachine UML-2.5.1 State, State::/isSubmachineState, submachine, State::entry, State::doActivity, State::exit, State::submachine, State::containingStateMachine()
WARNING The difference between Dependency and Usage in UML is notoriously vague. SysML-1.6, UML-2.5.1 Dependency, Usage
OPTION The default display of all tagged values on the comment symbol for an ElementGroup can make diagrams cluttered, but you can extend it with a custom stereotype and customise the default visible tagged values. tagged value, stereotype Property, user defined Stereotype, Stereotype, custom Stereotype, MD:Customization ElementGroup, ElementGroup::name, ElementGroup::/size, ElementGroup::/criterion, ElementGroup::/member, ElementGroup::orderedMember
CAVEAT The custom DiagramDescription stereotype is not specified (in SysML1.6) SysML-1.6
TIP THE BIG TIP: You brain has many facets: code + graphical engineering is greater than either alone Mathematica, Systems Modeling Language, MagicDraw, CATIA Magic, Cameo Systems Modeler, Magic Model Analyst, Model-Based Systems Engineering, model-based development, SysML
TIP The ActivityEdge, Transition, and Connector metaclasses do not extend (directly or indirectly) the Relationship metaclass (although the notations for them do indicate a kind of "relationship"). ActivityEdge, Transition, Connector, Relationship, DirectedRelationship
GOTCHA, ISSUE, WARNING SysPhSLibrary and ISO-80000 ModelLibrary: Some ValueType names and Unit symbols are not Modelica-friendly ValueType, ValueType::unit, Unit SysPhS, Modelica, ISO-80000
MODELLING, TIP, TOOL SysPhS: MagicDraw/Cameo: In the sysphs_profile the properties for PhSVariable have multiplicity [1], so the defaults always appear explicitly (but may be overridden): isContinuous: Boolean = true, isConserved: Boolean = false, changeCycle: Real = 0 SysML-1.6, SysML-1.7, SysPhS-1.1 stereotype Property, Stereotype, multiplicity SysPhS, SysML, Systems Modeling Language, Cameo Systems Modeler, MagicDraw SysML
ISSUE, TOOL SysPhS: MagicDraw/Cameo v19SP3: Export to Modelica does not interpret as 'start' the default on a PhSVariable assigned via ElementValue to a PhSConstant SysML-1.6, SysML-1.7, SysPhS-1.1 MD:ElementValue, MagicDraw:ElementValue, Property::defaultValue SysPhS, MD SysML, MagicDraw SysML, Cameo Systems Modeler
ASSERTION, TIP SysPhS: GOTCHA: By default PhSConstant maps to a Modelica parameter (not to a Modelica constant) SysPhS-1.1 value property SysPhS, Modelica
ISSUE SysPhS-1.1: [TRIVIAL] p.11: If property 'm:Mass' is named then ':Ground' should also be named for consistency in 'Figure 2: Association block with internal structure and connector properties in SysML' SysPhS-1.1 SysPhS
TIP SysPhS-1.1: When RealSignalInElement or RealSignalOutElement are used to type a SysML Port, assignments to the FlowProperty 'rSig' map to the Port name (only) when mapped to Modelica. SysML-1.6, SysML-1.7, SysPhS-1.1 Port FlowProperty
ISSUE, TOOL SysPhS-1.1: Use of 'Criteria = u2~=0' for Simulink for Real.Routing.Switch::u2 inconsistent with BooleanInput of control port Modelica.Blocks.Logical.Switch::u2 SysPhS-1.1 SysPhS, MagicDraw SysML, Cameo Systems Modeler, Modelica, Simulink
ISSUE SysPhS-1.1: Typos: Numerous references to 'rsig' lower case should be 'rSig' (including Figure 25 and Figure 29) SysPhS-1.1 SysPhS
PROPOSAL SysPhS-1.1: TwoPinElectricalComponent in 'Figure 39: Electrical blocks, ports & component properties' could be marked abstract SysPhS-1.1 Classifier::isAbstract Block SysPhS, SysML
ISSUE SysPhS-1.1: The correct ValueTypes should be used throughout instead of just Real for constraint parameters in 'Figure 61: Hydraulics model constraint blocks' SysPhS-1.1 ValueType, Real SysPhS
ISSUE SysPhS-1.1: The correct ValueTypes for Current, Voltage, Resistance, Capacitance, and Inductance should be used throughout instead of just Real in 'Figure 40: Circuit constraint blocks' SysPhS-1.1 ValueType, Real SysPhS
ISSUE, PROPOSAL SysPhS-1.1: Suggest use connector forms 'Modelica.Blocks.Interfaces.RealInput u;' and 'Modelica.Blocks.Interfaces.RealOutput y;' not 'input Real u;' and 'output Real y;' in Modelica code examples (otherwise not connectable). SysPhS-1.1 SysPhS
CAVEAT SysPhS-1.1: SourceAndSink.Clock does not have 'offset' or 'startTime' to match Modelica's Clock SysPhS-1.1 SysPhS, Modelica
ISSUE SysPhS-1.1: RelativeHumidityScenario1: Figure 98: Relative Humidiity Scenario Initial Values: RelativeHumidity should be RelativeHumidity1 SysPhS
ISSUE SysPhS-1.1: p.81: 'resistance:ViscousResistance' (in Figure 60) has to be treated as a PhSVariable not a PhSConstant, otherwise get an invalid system with 6 variables and 7 equations. Constraint ConstraintBlock SysPhS, hydraulics, fluid flow
ISSUE SysPhS-1.1: p.60: table for routing components: row for Switch: equivalents Modelica.Blocks.Logical.Switch (for Modelica) and Switch (for Simulink) missing SysPhS-1.1 SysPhS, Modelica, Simulink
ISSUE SysPhS-1.1: p.57: Table 11.3.2.5 Mathematical components: Modelica Parameters for the Subtraction row should indicate (k1 and) k2 required to achieve subtraction via Math.Add (or the correct exported values should be explained). SysPhS-1.1 SysPhS, Modelica, Simulink
TIP, WARNING SysPhS-1.1: p.57: GOTCHA: Table 11.3.2.5 Mathematical components: Mathematical.Subtraction maps to Math.Add (in Modelica) and Sum (in Simulink) SysPhS-1.1 SysPhS, Modelica, Simulink
ISSUE SysPhS-1.1: p.53: Figure 30: Incorrect references to RealInSignalElement, RealOutSignalElement, IntegerInSignalElement, IntegerOutSignalElement, BooleanInSignalElement, BooleanOutSignalElement (should be RealSignalInElement, RealSignalOutElement, ...) SysPhS-1.1 SysPhS
ISSUE SysPhS-1.1: p.47: 10.12.2 SysML modeling: TYPO: Incorrect spelling of RealInSignalElement (should be RealSignalInElement) and RealOutSignalElement (should be RealSignalOutElement) SysPhS-1.1 StateMachine SysPhS
ISSUE SysPhS-1.1: p.47: 10.12.2 SysML modeling: The states StandBy and On in 'Figure 29: State machine in SysML' should probably use 'entry' not 'doActivity'. SysPhS-1.1 State::entry, State::doActivity, StateMachine SysPhS, SysML, Systems Modeling Language
ISSUE SysPhS-1.1: p.47: 10.12.2 SysML modeling: References to 'u.sigsp' and 'y.usigsp' should be 'u.rSig' and 'y.rSig'. SysPhS-1.1 SysPhS
ISSUE SysPhS-1.1: p.45: 10.11.2 SysML modeling: Reference to 'the units library in Figure 20, Subclause 11.2.2' is wrong SysPhS-1.1 SysPhS
ISSUE SysPhS-1.1: p.44: 10.10.3 Modelica modeling: Reference to 'The following Modelica code corresponds to Figure 15' should probably be 'to Figure 27'. SysPhS-1.1 SysPhS
ISSUE SysPhS-1.1: p.42: 10.9.8 Modelica modeling, physical interaction: Modelica code has 'forcediff=springcst*lengthchg;' should be 'forcethru=springcst*lengthchg;' SysPhS-1.1 SysPhS, Modelica
ISSUE SysPhS-1.1: p.41: 10.9.8 Modelica modeling, physical interaction: Reference to 'the bindings in Figure 14' should probably be 'the bindings in Figure 26'. SysPhS-1.1 SysPhS
ISSUE, PROPOSAL SysPhS-1.1: p.38: 10.9.4 Modelica modeling, signal flow: Suggest kick start Spring with something like 'position=5' (otherwise get flat line when run). SysPhS-1.1 SysPhS
ISSUE SysPhS-1.1: p.38: 10.9.4 Modelica modeling, signal flow: Modelica code: the keyword should be 'equation' not 'equations'. SysPhS-1.1 SysPhS, Modelica
ISSUE SysPhS-1.1: p.38: 10.9.4 Modelica modeling, signal flow: Modelica code: the equation 'der(velocity)=(u-springcst*position)/m;' should use variable 'mass' not 'm' SysPhS-1.1 SysPhS, Modelica
ISSUE SysPhS-1.1: p.38: 10.9.4 Modelica modeling, signal flow: Example Modelica model should be for SpringMassSys not Spring SysPhS-1.1 SysPhS
ISSUE SysPhS-1.1: p.32: 10.7.8 Modelica modeling, physical interaction: Type Real for 'f' and 'lV' in example Modelica code for Spring do not correspond to 'Figure 23: Ports for physical interaction in SysML', should be Force and Velocity. SysPhS-1.1 SysPhS, Modelica, Wolfram SystemModeler
ISSUE SysPhS-1.1: p.30: text and Figure 22: Incorrect references to 'RealInSignalElement' and 'RealOutSignalElement' (should be RealSignalInElement, RealSignalOutElement) SysPhS-1.1 SysPhS
ISSUE SysPhS-1.1: p.30: 10.7.4 Modelica modeling, signal flow: Example Modelica code for Spring corresponding to 'Figure 22: Ports for signal flow in SysML' is invalid [should probably be 'input Real u;' and 'output Real y;' not 'in ...' and 'out ...'] SysPhS-1.1 SysPhS, Modelica, Wolfram SystemModeler
ISSUE SysPhS-1.1: p.28: 10.6.3 Modelica modeling: An assigned value “...” is shown for v3 in the Modelica code but none is shown in the SysML model in 'Figure 21: PhSVariables and PhSConstant in SysML' (and “...” is not compatible with Real). SysPhS-1.1 SysPhS, Modelica, Wolfram SystemModeler
ANTI-PATTERN SysPhS-1.1: In the specification model for Figure 59 the handling of the initial values for some value properties (such as for 'gravity') in Tank usages within context block ConnectedTanks is WET not DRY (breaks Single Source of Truth). SysPhS-1.1 Don't Repeat Yourself, WET, We Enjoy Typing, Single Source of Truth, SSoT
COMPLICATION, TOOL, WARNING SysPhS-1.1: GOTCHA: The term "initial values" is sometimes just used to refer to the start values for a simulation run in Modelica or Simulink. It does NOT always mean the additional context-specific values mechanism of SysML beyond Property::defaultValue Property::defaultValue, Property::redefinedProperty initial values, context-specific values SysML, Systems Modeling Language, MagicDraw SysML, MD SysML, Cameo Systems Modeler, system configuration, deep configuration, modes, SysPhS
ISSUE, LIMITATION SysPhS-1.1: Does not support Modelica's encapsulated enumeration. SysPhS-1.1 Modelica, SysPhS
ISSUE, LIMITATION SysPhS-1.1: Does not support Modelica's conditional declaration form. SysPhS-1.1 Modelica, SysPhS
ISSUE, LIMITATION SysPhS-1.1: Does not support Modelica's 'min' or 'max' on type declarations SysPhS-1.1 ValueType SysPhS, Modelica
ISSUE, LIMITATION, WORKAROUND SysPhS-1.1: Does not support Modelica's 'initial equation'. WORKAROUND: One can often achieve the same by directly setting a default on a variable and/or by using additional variables/parameters with 'start' and additional equations. SysPhS-1.1 Property::defaultValue SysPhS, Modelica
ISSUE, LIMITATION SysPhS-1.1: Does not support Modelica's 'experiment' annotations SysPhS-1.1 SysPhS, Modelica
ISSUE, MODELLING, STYLE SysPhS-1.1: Apparent use of part Property with «port» keyword (instead of standard SysML Port) leads to property path symbols appearing inside the boundary of context blocks (instead of within a Port symbol on the boundary) in IBDs and Parametric Diagrams SysPhS-1.1 «keyword», Port, Stereotype "standard" Port, block property, part property, SysML Internal Block Diagram, multi-level property path, pathname dot notation SysPhS
ISSUE SysPhS-1.1: Annex A.5: Typo in Figure 98 redefining value property 'C2 : Time = 1.0{redefines C2,unit = second}', should be lower case 'c2' (compare with BDD Figure 79) SysPhS-1.1 Property::redefinedProperty SysPhS
ISSUE SysPhS-1.1: Annex A.5: The BDD Figure 74 and Parametric Diagram Figure 84 for block RelativeHumidityCalculationConstraint are missing PhSConstant 'c2'. Compare with the constraint {der(x)=((press/satVap)-change)/c2} in BDD Figure 79. SysPhS-1.1 Constraint constraint parameter, value property SysPhS
ISSUE SysPhS-1.1: Annex A.5: redefinition 'humidifierSystem {redefines humidifierSystem}' incorrect in Figure 96: Humidifier System Scenario Initial Values SysPhS-1.1 Property::redefinedProperty SysPhS
ISSUE SysPhS-1.1: Annex A.5: p.89: Figure 75: Humidifier blocks, ports, & component properties. Typo in name of value property 'litpSec2mLiptHr:Real' on WaterTank should be 'litpSec2mLitpHr:Real' (breaks export of redefining Property with correct name). SysPhS-1.1 Property::redefinedProperty SysPhS
ISSUE, MODELLING SysPhS-1.1: Annex A.5: Humidifier: Use of UML-style direct Port conjugation not permitted since SysML-1.6, prefer ~InterfaceBlock type-based conjugation (example requires migration) SysML-1.6, SysML-1.7, SysPhS-1.1 Port::isConjugated ~InterfaceBlock SysPhS
ISSUE SysPhS-1.1: Annex A.5: Humidifier: Naming not very consistent across parts, input/output Port name, value properties, or constraint parameters SysPhS-1.1 Port "standard" Port, Block, block property, constraint parameter, value property SysPhS
ISSUE SysPhS-1.1: Annex A.5: Humidifier: Constraints on RelativeHumidityCalculationConstraint not consistent between BDD Figure 79 and Par Figure 84 (does not have 'c2') SysPhS-1.1 SysPhS
ISSUE SysPhS-1.1: Annex A.5: Humidifier: Constraints on HeatingCalculationConstraint not consistent between BDD Figure 79 and Par Figure 88 (does not have 'c1') SysPhS-1.1 SysPhS
ISSUE SysPhS-1.1: Annex A.5: 'Figure 101: Heating Scenario Initial Values': HeatingCalculation1: no such value to redefine 'C1 : Time = 1.0{redefines C1,unit = second}', should be 'xIntg : Real' (compare with BDD Figure 77 and Parametric diagram Figure 88) SysPhS-1.1 Property::redefinedProperty SysPhS
ISSUE SysPhS-1.1: 10.12.2 SysML modeling: p.47: Name of StateMachine in 'Figure 29: State machine in SysML' should be ComputerSM (not Computer) for consistency with the Modelica code example SysPhS-1.1 StateMachine SysPhS
ISSUE SysPhS-1.1: 10.12.2 SysML modeling: p.47, p.48: References to .sig and .rsig in 'Figure 29: State machine in SysML' and Modelica code example should be .rSig SysPhS-1.1 StateMachine SysPhS
TIP SysPhS-1.1 vs Modelica: On export the SysPhS signal flow Port types are flattened to remove the FlowProperty (rSig, iSig, or bSig). In the exported Modelica code you'll only ever see the Port names. Port "standard" Port SysPhS, Modelica
ISSUE SysPhS-1.1 spec version of 'Figure 48: Internal structure of the signal processor' shows an ItemFlow for Real on an overlapping Connector line section, which is impossible to interpret. SysPhS-1.1 Connector SysPhS
ISSUE SysPhS-1.1 spec version of 'Figure 38: Internal structure of the circuit example' shows some bi-directional ItemFlows for Charge on overlapping Connector line sections, which are impossible to interpret. SysPhS-1.1 Connector SysPhS
ISSUE, TOOL SysPhS-1.1 (and MDSysML/Cameo 19SP3 SysPhSLibrary): Use of RealSignalInElement for Real.Routing.Switch::u2 inconsistent with BooleanInput of control port Modelica.Blocks.Logical.Switch::u2 SysPhS-1.1 SysPhS, MagicDraw SysML, Cameo Systems Modeler, Modelica
ISSUE, LIMITATION, WARNING SysPhS vs Modelica: If you redeclare a PhSConstant (Modelica parameter) as a PhSVariable (Modelica variable) Modelica still treats it as a 'parameter'. You can end up with an unbalanced system with one equation too many! SysPhS-1.1 Property::redefinedProperty ValueType SysPhS, Modelica
MODELLING SysMLv2: On the v2 Comment extension of the v2 AnnotatingElement as a candidate Parsing Analysis Container SysML-1.6, SysML-1.7, UML-2.5.1 WPA:«snippet», WPA:«pa»