Gallery: SysML Parsing Analysis: The Hybrid Sports Utility Vehicle (SUV) sample problem in MD SysML (from 2007-2008)
Annotated versions: a UML™ Parsing Analysis of the SysML1.0 spec vs. sample problem diagrams:
Introduction to the Hybrid Sports Utility Sample project for MagicDraw SysML
Navigation tips: for the MD SysML sample
Profiles used in the MD SysML sampl
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
.jpg)
Figure B.11 - Establishing HSUV Requirements Hierarchy (containment)
Figure B.11a HSUV Requirements: Alternative: use «containment» wrapper Components
Figure B.11b HSUV Requirements: Alternative: stereotype UML Components as SysML «requirement»s (non standard)
Figure B.12 - Establishing Derived Requirements and Rationale from Lowest Tier of Requirements Hierarchy
Figure B.13 - Acceleration Requirement Relationships
.jpg)
Figure B.15 - Defining the Automotive Domain (Automotive Domain Breakdown)
_0.jpg)
Figure B.16 - Defining Structure of the Hybrid SUV System (Hybrid SUV Breakdown)
Figure B.16a - Alternative: using «composition» wrappers for assemblies
Figure B.17 - Internal Structure of Hybrid SUV
.jpg)
Figure B.18 - Defining Structure of Power Subsystem (PowerSubsystem Breakdown)
_2.jpg)
Figure B.19 - Internal Structure of the Power Subsystem (Alternative 1 - Combined Motor Generator)
Figure B.19a PowerSubsystem BDD: part and port design with required/provided interfaces
_0.jpg)
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
.jpg)
Figure B.22 - Consolidating Interfaces into the CAN Bus (CAN Bus Description)
_1.jpg)
Figure B.23 - Elaborating Definition of Fuel Flow (Power Subsystem Fuel Flow Definition)
Figure B.24 - Defining Fuel Flow Constraints
FuelFlow.constraint_0.jpg)
Figure B.25 - Detailed Internal Structure of Fuel Delivery Subsystem (Fuel Distribution Detail)
_0.jpg)
Figure B.26 - Defining Analyses for Hybrid SUV Engineering Development (Analysis Context)
Figure B.27 - Establishing a Performance View of the User Model
_1.jpg)
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.33a - Behavior Model for Accelerate Function: alternative using Pins
_0.jpg)
Figure B.34 - Decomposition of Accelerate Function (Activity and Object Flow Breakdown)
Figure B.35 - Detailed Behavior Model for Provide Power (with Swimlane Allocation)
.jpg)
Figure B.36 - Flow Allocation to Power Subsystem (Power Functional Allocation)
.jpg)
Figure B.38 - Special Case of Internal Block Diagram Showing Reference to Specific Properties (Test Results) [NOT SUPPORTED]
WORKAROUND for Property-Specific Types for Hybrid SUV test results
Hybrid SUV Sample: additional diagrams:
Decomposition of Activity Operate Car: using Activity Decomposition Hierarchy Wizard
Figure 11.10 - Continuous system example 1: Operate Car
_0.png)
Figure 11.10 - Continuous system example 1: Operate Car (adapted to use Pins, no annotations)
Figure 16.3 - Requirements Derivation: Safety Test
Figure 16.4 - Links between requirements and design: MasterCylinderSafety
.png)
Figure 8.8 - Block diagram for the Wheel Package (WheelHubAssembly)
Figure 8.8 - WheelHubAssembly: alternative: how to use: composition wrappers
Figure 8.9 - Internal Block Diagram for WheelHubAssembly
HOWTO use property-specific default values: Hybrid SUVs with different size wheels
Default Values for small Hybrid SUV vehicle
Default Values for large Hybrid SUV vehicle
Allocation Tree for Provide Power Actions
Hybrid SUV Sample: OMG RTF versions, no annotations, no MagicDraw diagram 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)
_0.jpg)
Figure B.35: with Swimlane Allocation (with explicit Pin notation)
Figure B.36: Power Functional Allocation
- Printer-friendly version
- Login to post comments
The Doctor is in the house
Tag and Keyword Cloud
Syndicate
