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 Port required Interface provided Interface Interface Usage InterfaceRealization ball-and-socket lollipop Connector SysML keywords HSUV sample problem SysML Internal Block Diagram ItemFlow FlowProperty InterfaceBlock ~InterfaceBlock Slide kind SysML Internal Block Diagram (IBD) Click on the image to view it full size Up next Figure D.20 - Blocks Typing Ports in the Power Subsystem (ICE Port Type Definitions) Notes [ISSUE] SysML-1.6: Figure D.19 Internal Structure of the Power Subsystem (Internal Block Diagram): Connector 'acl-ecu' and 'bkp-ecu' should be 'acl-pcu' and 'bkp-pcu' [ISSUE] SysML-1.6: Figure D.19 has an unnecessary Comment with the name of the 'ctrl' Port [ISSUE] SysML-1.6: Figure D.19: It's not clear why 'Port:~FuelTankFitting' (an ~InterfaceBlock conjugation port) does not match 'Port:ICEFuelFitting' [NAMING, POLICY] DO NOT name ports with first letter capital (like 'Port'), DO NOT name ports 'port' (except for educational illustration), and DO NOT use port names that do not indicate a role. [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')! [CAPABILITY, FEATURE, STYLE, TIP] TIP: MagicDraw/Cameo: Consider showing the Port name and type label inside the Port symbol! CAVEAT: This loses the direction indicators on Ports typed by Blocks with flow properties (but is fine if ItemFlows show the direction, or for "contract ports"). [DISPLAY, STYLE] SysML directed features displayed on Port symbols are often far clearer than UML-style provided/required Interface "ball (lollipop) and socket" notation [ASSERTION, ISSUE] SysML-1.6: Needs a constraint on ~InterfaceBlock making the implied inversion of provided/required Interfaces explicit Snippets (quotes/extracts) [SysML-1.6] Figure D.19 shows how the parts of the PowerSubsystem block, as defined in the diagram above, are used. It shows connectors between parts, ports, and connectors with item flows. [SysML-1.6] The dashed borders on FrontWheel and BrakePedal denote the “use-not-composition” relationship depicted elsewhere in Figure D.16 and Figure D.18. [SysML-1.6] The dashed borders on Fuel denote a store, which keeps track of the amount and mass of fuel in the FuelTankAssy. This is also depicted in Figure D.18. Visit also Visit also (backlinks) Related slides (includes other tutorials) Related slides (backlinks, includes other tutorials) [HISTORICAL] UML-STYLE: Hybrid SUV example: Ports with required/provided Interfaces (Block Definition Diagram) [HISTORICAL] UML-STYLE: Hybrid SUV example: Ports with required/provided Interfaces (Internal Definition Diagram) Hybrid SUV example: provided/required DirectedFeatures (Block Definition Diagram) Hybrid SUV example: provided/required DirectedFeatures (Internal Definition Diagram) Using SysML ItemFlow on an Association to show compatibility with a physical flow ItemFlow without and with itemProperty - and compatible ItemFlows Conjugation in SysML-1.7 is Type-based: InterfaceBlock, ~InterfaceBlock, and DirectedFeature Flags Book traversal links for Figure D.19 - Internal Structure of the Power Subsystem (Internal Block Diagram) Previous Up Next
