- (12140) B.4.1.2 Package Diagram: <<access>> should be <<import>>
- (12141) B.4.4.3 Requirement Diagram: 'refineReqt' should just be 'refine'
- (12142) B.4.5.4 Block Definition Diagram: Should say 'white diamond (shared AggregationKind)' not 'white diamond (composition)'
- (12143) B.4.8.3 Activity Diagram (EFFBD): refers incorrectly to objectFlows in BDD Figure B.34
- (12146) Figure B.9: clarify turnIgnitionToStart message on driver:Driver
- (12160) Figure B.29: 'delta-t' shown with solid-line (AggregationKind 'composite'), not dashed line (AggregationKind 'none')
- B.4.8.3 Activity Diagram (EFFBD): refers to allocations to parts instead of blocks
- Figure B.10: justify 'StartVehicle' from outside in terms of UML
- Figure B.27: <<view>> Package "steals ownership" of MOEs, Actor, UseCase and Requirement
- Figure B.34 and Figure B.35: ownership of objectFlow 'elecDrivePower:ElecPower' inconsistent
- Figure B.35: prefer <<continuous>> pins over contrived placement of ObjectNodes on border of swimlanes
- Figure B.36 emg:ElectricalMotorGenerator should be allocated from a4:ProvideElectricPower not ConvertElectricToPower
- Figure B.36: ecu:PowerControlUnit should be allocated from ProportionPower, not ProportionPowerLoad
- Figure B.36: ice:InternalCombustionEngine should be allocated from ProvideGasPower, not ConvertGasToPower
- Figure B.36: shows allocations to part Properties, not to Blocks as in Figure B.35
- Figure B.37: the elements allocated from are of type Action, not Activity
- Figure B.38: property names of p:[PowerSubsystem] inconsistent w.r.t. other figures
- Figure B.9: explain how 'turnIgnitionToStart' message from outside system corresponds with UML
- The composing owner of FrontWheel is never made clear
- TODO Figure B.31, Figure 10.1: parameters 'x' and 'dt' (a.k.a. 'delta-t') missing in StraightLineVehicleDynamics
- TODO: 'ft:FuelTankAssy' -> 'ft:FuelTankAssembly': Figure 9.5, 9.4.1.1, B.4.5.5, Figure B.19, B.4.5.6, Figure B.25
- TODO: Fig B.26: referenced value property GlobalTime contradicts assertion that a value property has AggregationKind 'composite'
- TODO: Figure B.23: Can a block have flow properties and a FlowPort typed by a FlowSpecification with the same flow properties ?
- TODO: Figure B.23: The sense of direction seems the wrong way round in the Block flow properties and FlowSpecification
- TODO: Figure B.25: Why are the flowports typed by FuelFlow <<FlowSpecification>> never used ?
- TODO: Figure B.26: GlobalTime not clearly defined
- TODO: Figure B.28: parameter 'vc' of constraint property ':CapacityEquation' inconsistent w.r.t. CapacityEquation in Figure B.26
- TODO: Figure B.33: appears to use Dependencies (dashed) instead of control flows
- TODO: Figure B.33: suggest use in/out Pin pairs instead of <<continuous>> accelPosition ObjectNode
- TODO: Figure B.34 - Decomposition of “Accelerate” Function: should show Accelerate <<activity>>
- TODO: Figure B.38: has part typed by '[Interior]' rather than '[InteriorSubsystem]'
Dr Darren's MagicDraw UML and SysML Plugin eSchool
Motto: "Learn good ways to work with MagicDraw UML and its SysML Plugin !"
|
About the eSchool
UML2 in MagicDraw
MagicDraw UML tips
MD SysML Plugin
MagicDraw for Java
MagicDraw for XML
INCOSE2008: Tool Vendor Challenge (TVC)
Advanced UML and SysML Training
|
Annex B: Sample ProblemThu, 12/27/2007 - 11:42 — drkelly
|
Search
The MagicDraw SysML Plugin Tutorial Overview
|