MagicDraw UML and SysML Plugin eSchool
Motto: "Learn good ways to work with MagicDraw UML and its SysML Plugin !"
eSchool home
www.magicdraw.com
«UML2»
«FAQ»
«SysML»
«tips»
«Java»
«XML»
OMG
About the eSchool
About MagicDraw eSchool
About No Magic Inc.
About the OMG
About copyright
UML2 in MagicDraw
UML2 Tutorials
UML2 metaclasses
UML2 issues
MagicDraw UML tips
MagicDraw modeling
UML style tips
The UML Parsing Analysis recipe
MagicDraw UML FAQs
MagicDraw SysML Plugin
MagicDraw SysML metamodel
SysML Plugin tutorials
Example: The Hybrid Sports Utility Vehicle
SysML Plugin FAQs
OMG SysML issues
MagicDraw for Java
Reverse Java source
MagicDraw for Java tutorials
MagicDraw for XML
MagicDraw for XML tutorials
Advanced UML and SysML Training
MagicDraw UML, SysML, DoDaf, etc., training courses by No Magic.
Please click here
Home
»
Example: The Hybrid Sports Utility Vehicle
»
Hybrid SUV Sample: additional diagrams
»
Hybrid SUV (OMG RTF versions, no annotations, no MagicDraw symbols)
Figure B.18: Alternative 1 - Combined Motor Generator
Mon, 06/02/2008 - 11:01 — author
Visit also annotated version:
Figure B.19 - Internal Structure of the Power Subsystem
Image:
‹ Figure B.17: HybridSUV
up
Figure B.18: PowerSubsystem breakdown ›
Printer-friendly version
Login
to post comments
Search
The Hybrid Sports Utility Vehicle (SUV) sample problem
Introduction to the Hybrid Sports Utility Sample project for MagicDraw SysML
Figure B.2 - Defining ValueTypes and Units to be used in the sample problem
Figure B.3 - Establishing Structure of the User Model using Packages and Views (Package Diagram)
Figure B.4 - Establishing the Context of the Hybrid SUV System using a User-Defined Context Diagram
Figure B.5 - Establishing Top Level Use Cases for the Hybrid SUV
Figure B.6 - Establishing Operational Use Cases for Drive the Vehicle
Figure B.7 - Elaborating Black Box Behavior for the Drive the Vehicle Use Case
Figure B.8 - Finite State Machine Associated with Drive the Vehicle
Figure B.9 - Black Box Interaction for Start Vehicle, referencing White Box Interaction
Figure B.10 - White Box Interaction for StartVehicle
Figure B.11 - Establishing HSUV Requirements Hierarchy (containment)
Figure B.12 - Establishing Derived Requirements and Rationale from Lowest Tier of Requirements Hierarchy
Figure B.13 - Acceleration Requirement Relationships
Figure B.15 - Defining the Automotive Domain (Automotive Domain Breakdown)
Figure B.16 - Defining Structure of the Hybrid SUV System (Hybrid SUV Breakdown)
Figure B.17 - Internal Structure of Hybrid SUV
Figure B.18 - Defining Structure of Power Subsystem (PowerSubsystem Breakdown)
Figure B.19 - Internal Structure of the Power Subsystem (Alternative 1 - Combined Motor Generator)
Figure B.20 - Interfaces Typing StandardPorts Internal to the Power Subsystem (ICE Interface Definitions)
Figure B.21 - Initially Defining Flow Specifications for the CAN Bus
Figure B.22 - Consolidating Interfaces into the CAN Bus (CAN Bus Description)
Figure B.23 - Elaborating Definition of Fuel Flow (Power Subsystem Fuel Flow Definition)
Figure B.24 - Defining Fuel Flow Constraints
Figure B.25 - Detailed Internal Structure of Fuel Delivery Subsystem (Fuel Distribution Detail)
Figure B.26 - Defining Analyses for Hybrid SUV Engineering Development (Analysis Context)
Figure B.27 - Establishing a Performance View of the User Model
Figure B.28 - Defining Measures of Effectiveness and Key Relationships (HSUV MOEs)
Figure B.29 - Establishing Mathematical Relationships for Fuel Economy Calculations
Figure B.30 - Straight Line Vehicle Dynamics Mathematical Model
Figure B.31 - Defining Straight-Line Vehicle Dynamics Mathematical Constraints
Figure B.33 - Behavior Model for Accelerate Function
Figure B.34 - Decomposition of Accelerate Function (Activity and Object Flow Breakdown)
Figure B.35 - Detailed Behavior Model for Provide Power (with Swimlane Allocation)
Figure B.36 - Flow Allocation to Power Subsystem (Power Functional Allocation)
Figure B.38 - Special Case of Internal Block Diagram Showing Reference to Specific Properties (Test Results) [NOT SUPPORTED]
Hybrid SUV Sample: additional diagrams
Decomposition of Activity Operate Car: using Activity Decomposition Hierarchy Wizard
Figure 10.2 Definition of constraint blocks on a block definition diagram
Figure 11.10 - Continuous system example 1: Operate Car
Figure 16.3 - Requirements Derivation_ Safety Test
Figure 16.4 - Links between requirements and design: MasterCylinderSafety
Figure 8.8 - Block diagram for the Wheel Package (WheelHubAssembly)
Figure 8.9 - Internal Block Diagram for WheelHubAssembly
HOWTO use property-specific default values: Hybrid SUVs with different size wheels
Allocation Tree for Provide Power Actions
Hybrid SUV (OMG RTF versions, no annotations, no MagicDraw symbols)
Figure B.03: HSUV Model
Figure B.12: Requirement Derivation
Figure B.15: Automotive Domain Breakdown
Figure B.16: HybridSUV Breakdown
Figure B.17: HybridSUV
Figure B.18: Alternative 1 - Combined Motor Generator
Figure B.18: PowerSubsystem breakdown
Figure B.21: CAN Bus FlowSpecifications
Figure B.22: CAN Bus description
Figure B.23: PowerSubsystem Fuel Flow Definition
Figure B.24: Defining Fuel Flow Constraints
Figure B.25: Fuel Distribution Detail
Figure B.26: Analysis Context
Figure B.28: HSUV MOEs
Figure B.29: EconomyContext
Figure B.31: Definition of Dynamics
Figure B.33: Accelerate
Figure B.34: Activity and ObjectFlow breakdown
Figure B.35: with Swimlane Allocation (with elided Pin notation)