Sometimes a block lists its composite blocks as parts, and sometimes as properties

48 views
Skip to first unread message

avi-mak

unread,
Jun 15, 2020, 10:18:55 AM6/15/20
to SysML Forum
Hi,

This is a question on the difference between parts and properties. i want the question to be tool-agnostic, although I am using Sparx EA. And this is why I am sending the question to this forum and not to the EA forum (for the time being): I am looking for a SysML answer and not for an EA answer. (This may be just an EA quirk, but I don't think it is just a quirk.) 

Two level Block Hierarchy - Pattern.png

Below I present two similar design patterns available from EA, the 'One level Block Hierarchy' pattern and the 'Two level Block Hierarchy' pattern. In the first pattern the top level block lists its composite blocks as parts.  However, in the second pattern the top level block lists its composite blocks as properties. (And this apparent contradiction has expressed itself in my first diagrams.) 

What's going on ? 

EA - One level Block Hierarchy - Pattern available from Model Wizard 

One level Block Hierarchy - Pattern.png

EA - Two level Block Hierarchy - Pattern available from Model Wizard

Two level Block Hierarchy - Pattern.png

Thanks
Avraham





James Towers

unread,
Jun 17, 2020, 1:48:18 AM6/17/20
to SysML Forum
Hi Avraham,
Both are valid, however EA is just inconsistent here. The SysML spec says "Part, reference, value, and constraint properties may be shown in block definition compartments with the labels "parts," "references," "values," and "constraints" respectively. Properties of any type may be shown in a "properties" compartment or in additional compartments with user-defined labels."



On 15 Jun 2020, at 02:00, avi-mak <amak...@gmail.com> wrote:

Hi,

This is a question on the difference between parts and properties. i want the question to be tool-agnostic, although I am using Sparx EA. And this is why I am sending the question to this forum and not to the EA forum (for the time being): I am looking for a SysML answer and not for an EA answer. (This may be just an EA quirk, but I don't think it is just a quirk.) 

<Two level Block Hierarchy - Pattern.png>

Below I present two similar design patterns available from EA, the 'One level Block Hierarchy' pattern and the 'Two level Block Hierarchy' pattern. In the first pattern the top level block lists its composite blocks as parts.  However, in the second pattern the top level block lists its composite blocks as properties. (And this apparent contradiction has expressed itself in my first diagrams.) 

What's going on ? 

EA - One level Block Hierarchy - Pattern available from Model Wizard 

<One level Block Hierarchy - Pattern.png>

EA - Two level Block Hierarchy - Pattern available from Model Wizard

<Two level Block Hierarchy - Pattern.png>

Thanks
Avraham






--
--
You received this message because you are subscribed to the Google
Groups "SysML Forum" group.
Public website: http://www.SysMLforum.com
To post to this group, send email to sysml...@googlegroups.com
To unsubscribe from this group, send email to
sysmlforum+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sysmlforum?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "SysML Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sysmlforum+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sysmlforum/2f9a9e6d-9956-421f-b48c-9015357fb487o%40googlegroups.com.
<Two level Block Hierarchy - Pattern.png><One level Block Hierarchy - Pattern.png><Two level Block Hierarchy - Pattern.png>

avi-mak

unread,
Jun 17, 2020, 8:29:03 PM6/17/20
to SysML Forum
Great thanks, James.
I thought I had messed up, and did not understood EA user methodology.

-avraham



On Wednesday, June 17, 2020 at 8:48:18 AM UTC+3, James Towers wrote:
Hi Avraham,
Both are valid, however EA is just inconsistent here. The SysML spec says "Part, reference, value, and constraint properties may be shown in block definition compartments with the labels "parts," "references," "values," and "constraints" respectively. Properties of any type may be shown in a "properties" compartment or in additional compartments with user-defined labels."

On 15 Jun 2020, at 02:00, avi-mak <amak...@gmail.com> wrote:

Hi,

This is a question on the difference between parts and properties. i want the question to be tool-agnostic, although I am using Sparx EA. And this is why I am sending the question to this forum and not to the EA forum (for the time being): I am looking for a SysML answer and not for an EA answer. (This may be just an EA quirk, but I don't think it is just a quirk.) 

<Two level Block Hierarchy - Pattern.png>

Below I present two similar design patterns available from EA, the 'One level Block Hierarchy' pattern and the 'Two level Block Hierarchy' pattern. In the first pattern the top level block lists its composite blocks as parts.  However, in the second pattern the top level block lists its composite blocks as properties. (And this apparent contradiction has expressed itself in my first diagrams.) 

What's going on ? 

EA - One level Block Hierarchy - Pattern available from Model Wizard 

<One level Block Hierarchy - Pattern.png>

EA - Two level Block Hierarchy - Pattern available from Model Wizard

<Two level Block Hierarchy - Pattern.png>

Thanks
Avraham






--
--
You received this message because you are subscribed to the Google
Groups "SysML Forum" group.
Public website: http://www.SysMLforum.com
To post to this group, send email to sysml...@googlegroups.com
To unsubscribe from this group, send email to

For more options, visit this group at
http://groups.google.com/group/sysmlforum?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "SysML Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sysml...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages