Figure D.25 - Detailed Internal Structure of Fuel Delivery Subsystem (Internal Block Diagram)

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: HSUV sample

Tags and keywords

UML keywords

SysML keywords

MD:PartProperty

Slide kind

SysML Internal Block Diagram (IBD)

Click on the image to view it full size

In the trail version of the diagram, the outgoing and incoming port types for the flow of Fuel are named F_Fuel and ~F_Fuel (not shown on every Port). The spec has these Port types as Fuel:

Webel Best Practice: Webel: DO NOT name the Type (Block or InterfaceBlock) of a Port with a flow the same as the name of the 'Stuff' that flows through it; use the Webel 'F_Stuff' convention!

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)

Up next

Figure D.26 - Defining Analyses for Hybrid SUV Engineering Development (Block Definition Diagram)

Notes

[CONVENTION, NAMING]{STRICT} Webel: DO NOT name the Type (Block or InterfaceBlock) of a Port with a flow the same as the name of the 'Stuff' that flows through it; use the Webel 'F_Stuff' convention!

[ISSUE] SysML-1.6: Need a Connector from fuel:Fuel to :FuelPump in 'Figure D.25 Detailed Internal Structure of Fuel Delivery Subsystem (Internal Block Diagram)'

[CAPABILITY, FEATURE, TIP, TOOL] MagicDraw/Cameo: you can make relationships between elements that are not visible in one diagram using the Relations section of the specification dialog for an element

[POLICY] For Blocks and Interface blocks with one or more FlowProperty items, choose a direction convention and use it across one project.

[ISSUE] 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)

Snippets (quotes/extracts)

[SysML-1.6] Figure D.25 shows how the connectors fuelDelivery and fdist on Figure D.19 have been expanded to include design detail. The fuelDelivery connector is actually two connectors, one carrying fuelSupply and the other carrying fuelReturn.

[SysML-1.6] The fdist connector inside the InternalCombustionEngine block has been expanded into the fuel regulator and fuel rail parts. These more detailed design elements are related to the original connectors using the allocation relationship.

[SysML-1.6] The Fuel store represents a quantity of fuel in the FuelTankAssy, which is drawn by the FuelPump for use in the engine, and is refreshed, to some degree, by fuel returning to the FuelTankAssy via the FuelReturnLine.

[SysML-1.6] Allocate is a dependency based on UML::Abstraction. It is a mechanism for associating elements of different types, or in different hierarchies, at an abstract level. Allocate is used for assessing user model consistency and directing future design ...

[SysML-1.6] It is expected that an «allocate» relationship between model elements is a precursor to a more concrete relationship between the elements, their properties, operations, attributes, or sub-classes.

[SysML-1.6] Allocate is directional in that one NamedElement is the "from" end (no arrow), and one NamedElement is the "to" end (the end with the arrow).

Visit also

Visit also (backlinks)

Related slides (includes other tutorials)

Related slides (backlinks, includes other tutorials)

Flags