Gallery: SysML1.0 issues (2007-2008)
(11066) Namespace compartment for blocks
(11275): 8.3.2: Unit/Dimension Notation "to underline or not to underline"
(11493) Lack of notation for units and dimensions on values
UseValued
(11622) Mapping of PropertySpecificType to the UML metamodel
RedfinitionContextForSystem BDD analysis of: 11622 Mapping of PropertySpecificType to the UML metamodel
The first-level usage, no redefinition of properties, no property-specific types
(12128) Suggest Unit and ValueType both extend abstract DimensionedType, and inherit a 'dimension' attribute(12219) A stereotype for a Quantity is required.
[Suggest show both part-specific values & static values "showing through" to part within a value context with static indicator]
(10059) 'Interfaces on Flow Ports': Recommend use nested ports: Hydraulic Morse System
(10059) 'Interfaces on Flow Ports'
(10342) 'Section: 9.3.2.8 ItemFlow: CASE STUDY: Signal'
CommunicationSystem
(10342) 'Section: 9.3.2.8 ItemFlow'
(10371) RECOMMEND: use both default value "callout" into a note and 'initial values' compartment in an IBD
UseBattery
(11599) "Fix for Fig 9.4 p70"
11599 Figure 9.4 - Interfaces 'ctrl' standard port of InternalCombustionEngine
(11628) Consider nested ports
Context for nested ports example
.jpg)
12222) 9.3.2.3 FlowPort, 9.3.2.7 Standard Port: formally permit useful idiom of flowport nested within standard port
8.4.4 Water Delivery: using nested ports
House IBD: using nested ports
HiFi with headphone port with audio flowport ports being produced and consumed by ports with HiFi flowports
example_of_nested_flowport_HiFi_producer_consumer (BDD)
relaying part Property (with SysML NestedConnectorEnd) vs relaying Port
relaying part Property vs relaying Port (BDD)
(10524) Constraint parameter stereotype
(11495) Constraint parameter notation conflicts with UML private ports notation
(11501) Wrong ends of Allocate relationship used in Allocated definition
(12134) «rate» stereotype has property 'rate' type ValueSpecification in 11.3.2.8 Rate yet InstanceSpecification in Figure 11.8 
SysML1.0: Figure 11.10 - Continuous system example 1
_0.png)
Figure 11.10 - Continuous system example 1 in MD_SysML_15 using Pins wherever possible
Figure 11.10 - Continuous system example 1 in MD_SysML_15 with detailed annotations on spec and tool issues
Permit UseCase <> from UML
Figure B.6
Figure B.27: <> Package "steals ownership" of MOEs, Actor, UseCase and Requirement
.png)
Figure B.35: prefer <> pins over contrived placement of ObjectNodes on border of swimlanes
Figure B.33: suggest use in/out Pin pairs instead of <> accelPosition ObjectNode
- Printer-friendly version
- Login to post comments
The Doctor is in the house
Tag and Keyword Cloud
Syndicate
