Issue 15295: SysML 1.2 Issues: Default <block> stereotype on unlabeled box is not always optimal (sysml-rtf)
Source: Change Vision (Mr. Michael Jesse Chonoles, mjchonoles(at)yahoo.com)
Nature: Uncategorized Issue
Severity: 
Summary: Page 36, 8.3.1.1  Default «block» stereotype on unlabeled box is not always optimal

 

Original Text

Default «block» stereotype on unlabeled box 
If no stereotype keyword appears within a definition box on a block definition diagram (including any stereotype property compartments), then the definition is assumed to be a SysML block, exactly as if the «block» keyword had appeared before the name in the top compartment of the definition. 

Comment

I question whether this is always desirable, e.g.,

1)       if the diagram had the «functional hierarchy» diagram usage stereotype applied, wouldn’t the default be «activity»,

2)       if the containing block is an activity block, wouldn’t  «activity» be the right default

 

Type: Clarification/Fix

               Add sentences that say: If the bdd diagram has a «diagram usage» specified (such as «functional hierarchy»), a different default (such as «activity») can be used. 

 

If the bdd diagram is for an activity block, the default stereotype elements is «activity»

 

Resolution: Defer

Postponed to the next RTF
Revised Text: 
Actions taken:
June 21, 2010: received issue
January 3, 2017: Deferred
April 6, 2017: closed issue
Discussion: 

End of Annotations:=====
te: Mon, 21 Jun 2010 16:54:09 -0400
From: "Chonoles, Michael J" <michael.j.chonoles@lmco.com>
Subject: New SysML 1.2 Issues: Default <block> stereotype on unlabeled box is not always optimal
To: Juergen Boldt <juergen@omg.org>
Cc: "sysml-rtf@omg.org" <sysml-rtf@omg.org>
Thread-Topic: New SysML 1.2 Issues: Default <block> stereotype on unlabeled box is not always optimal
Thread-Index: AcsRgRgR/KpB7ZW+Ti29XLehntb2nQAAE3hAAACEdtA=
Accept-Language: en-US
acceptlanguage: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 


Page 36, 8.3.1.1  Default «block» stereotype on unlabeled box is not always optimal

 

Original Text

Default «block» stereotype on unlabeled box 
If no stereotype keyword appears within a definition box on a block definition diagram (including any stereotype property compartments), then the definition is assumed to be a SysML block, exactly as if the «block» keyword had appeared before the name in the top compartment of the definition. 

Comment

I question whether this is always desirable, e.g.,

1)       if the diagram had the «functional hierarchy» diagram usage stereotype applied, wouldn.t the default be «activity»,

2)       if the containing block is an activity block, wouldn.t  «activity» be the right default

 

Type: Clarification/Fix

               Add sentences that say: If the bdd diagram has a «diagram usage» specified (such as «functional hierarchy»), a different default (such as «activity») can be used. 

 

If the bdd diagram is for an activity block, the default stereotype elements is «activity»