Figure 8-17: Vehicle specialization

Gallery
Tutorial
TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]
Section
Section: SysML-1.6 specification diagrams: 08 Blocks
UML keywords
Property::redefinedProperty
SysML keywords
BoundReference
Block
Slide kind
SysML Block Definition Diagram (BDD)
Click on the image to view it full size
SysML-1.6: Figure 8-17: Multiplicity of 'cylinderBR' in 'Vehicle Model 1' should be [4] not [*]
SysML-1.6: Figure 8-17: Multiplicity of 'rollBarBR' in 'Vehicle Model 1' should be [1] not [*] and it has no redefined type for the 'light roll bar'
SysML-1.6: Figure 8-17: Multiplicity of 'lugBoltBR' of 'Vehicle Model 1' should be [6] not [6..8]
SysML-1.6: Figure 8-17: EndPathMultiplicity is applied to 'rollBarBR' instead of 'lugBoltBR' of 'Vehicle Model 2'
SysML-1.6: Figure 8-17: Multiplicity of rollBarBR should be [0] not [*] in 'Vehicle Model 2'
SysML-1.6: Figure 8-17: Redefined properties in Vehicle Model 1 and Vehicle Model 2 break constraint: 'BoundReferences shall not be applied to properties that are related by redefinition to other properties with BoundReference applied'
It's also not entirely clear whether the multiplicity of lugBoltBR Vehicle Model 2 should be [*].
Webel Best Practice does not recommend block names with spaces like Chassis Assembly or Vehicle Model 1:
DO NOT use spaces in Property names or Class/Block names! If you want to communicate familiar names of elements within an organisation use a custom stereotype and tagged values (such as 'aka')!
Up next
Figure 8-18: Example of Unit, QuantityKind and ValueType definitions
Notes
[ISSUE] SysML-1.6: Figure 8-17: Multiplicity of 'cylinderBR' in 'Vehicle Model 1' should be [4] not [*]
[ISSUE] SysML-1.6: Figure 8-17: Multiplicity of 'rollBarBR' in 'Vehicle Model 1' should be [1] not [*] and it has no redefined type for the 'light roll bar'
[ISSUE] SysML-1.6: Figure 8-17: Multiplicity of 'lugBoltBR' of 'Vehicle Model 1' should be [6] not [6..8]
[ISSUE] SysML-1.6: Figure 8-17: EndPathMultiplicity is applied to 'rollBarBR' instead of 'lugBoltBR' of 'Vehicle Model 2'
[ISSUE] SysML-1.6: Figure 8-17: Multiplicity of rollBarBR should be [0] not [*] in 'Vehicle Model 2'
[NAMING, POLICY]{STRICT} DO NOT use spaces in Property names or Class/Block names! If you want to communicate familiar names of elements within an organisation use a custom stereotype and tagged values (such as 'aka')!
[ISSUE]{EDITORIAL} SysML-1.6: Figure 8-17: Redefined properties in Vehicle Model 1 and Vehicle Model 2 break constraint: 'BoundReferences shall not be applied to properties that are related by redefinition to other properties with BoundReference applied'
Snippets (quotes/extracts)
  [SysML-1.6] Figure 8-17 shows specializations for vehicles that restrict aspects of nested parts by redefining bound references. Paths for bound references are based on the property paths of the corresponding binding connectors.
  [SysML-1.6] The general block on the top does not restrict the bound properties, except the total number of lug bolts is required to be between 24 and 32, rather than 24 and 40 as the associations in Figure 8-15 allow.
  [SysML-1.6] The specialization on the lower left restricts the number of cylinders to four, requires a light roll bar, and a total of 24 lug bolts over all the wheels.
  [SysML-1.6] The specialization on the lower right restricts the number of cylinders to between six and eight, rules out any roll bar, and limits lug bolts per wheel to between 6 and 7, by giving the end path upper and lower values.
  [SysML-1.6] BoundReference::7_cannot_redefine_boundreference BoundReferences shall not be applied to properties that are related by redefinition to other properties with BoundReference applied.
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)