Bug 478264 - [SysML 1.4][Parametric] Port-like notation for constraint parameters (and value properties)
Summary: [SysML 1.4][Parametric] Port-like notation for constraint parameters (and val...
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: SysML (show other bugs)
Version: 0.8.0   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-24 03:32 EDT by Klaas Gadeyne CLA
Modified: 2017-02-17 07:28 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Klaas Gadeyne CLA 2015-09-24 03:32:39 EDT
[quote]
10.3.1.2.3 Small square box notation for an internal property
A value property may optionally be shown by a small square box, with the name and other specifications appearing in a text string close to the square box. The text string for such a value property may include all the elements that could ordinarily be used to declare the property in a compartment of a block, including an optional default value. The box may optionally be shown with one edge flush with the boundary of a containing property. Placement of property boxes is purely for notational convenience, for example to enable simpler connection from the outside, and has no semantic significance. If a connector is drawn to a region where an internal property box is shown flush with the boundary of a containing property, the connector is always assumed to connect to the innermost property.
[/quote]

Not particularly clear IMO, since the spec only talks of 'value properties' here, and not of "constraint parameters".  AFAICT The spec fails to give a formal definition of "constraint parameters", but it can be inferred from several places that 'value properties' in the context of a constraintBlock should be used to represent the constraint's parameters (see for instance the statements in bug #478259)

Table 10.2 shows how this should be done.  Especially for the constraint parameters, the 'flushed with boundary' port-like notation is always used consistently in the spec, see fi. Figure D24, D.31 and D.33 (nested constraint properties)
Comment 1 Klaas Gadeyne CLA 2015-09-24 03:37:08 EDT
FWIW, I don't know whether (a part of) the solution consist of treating constraint parameters _graphically_ as being ports and then use css rules to display the ports on the inside (see https://wiki.eclipse.org/Papyrus/Mars_Work_Description/NewFeature/Shape_customisation#Port_position)

In that case, this bug depends on Bug #472167, in which I argue that the portposition css syntax does not work for the composite structure diagram (of which the parametric diagram inherits)
Comment 2 Patrick Tessier CLA 2015-11-03 05:52:55 EST
create a parameter (poperty) as  border box  is not a problem ,