Messages

1

General Board / Re: SysML Itemflows and directionality in general

« on: August 10, 2021, 08:31:12 pm »

Hi Peter,

Thank you for your reply, I have had some success with this and have created an inout ports by typing by a block with an inout flow property and I have the nice bi-directional indication in the port itself.

However on another port, the one where I want Item flow, the ports are not bi-directional i'm not having the same success.
The block typing the port in this case is not bi-directional but in:video, out:video so it is point to point information flow which I have managed to create by;

Right clicking the connector
Advanced -> information flow realised -> set the type -> set source and target

So I have a point to point unidirectional flow indicated by the typing block and the item flow, however the ports are still showing arrows in both directions like the old non-atomic ports rather than a single arrow like the atomic flow ports.

Any ideas where I might be going wrong?

2

General Board / SysML Itemflows and directionality in general

« on: August 09, 2021, 11:05:12 pm »

Hi all,

I haven't been able to find how to add directionality to my connectors.

I'm using v1.4 so no atomic flow ports.

So I have an interface block to type the port for example DVI (Video) I could have invideo outvideo as basic flow properties.

How do I represent the direction flow on my IBD connectors? Does anybody have a link to an item flow user guide or is it still possible to annotate the directions on the port outside of the naming?

Is it as simple as going to andvanced and indicating direction on the connector via source to destination or vice versa?

......

I may have answered my own question. I right clicked on the connector, clicked item flow realised, selected the same block that typed the ports and then indicated the direction. Please let me know if this correct.

Many thanks in advance to the gurus out there.

Ray

3

General Board / Re: Modelling LANs and VLANS in sysml

« on: August 04, 2021, 03:48:27 am »

Hi qwerty, thanks, the only example model I found was the distiller example. Do you know where I can find this one?

Thanks

Ray

4

General Board / Re: EA only recognising aggregation and not reference connectors

« on: August 04, 2021, 01:57:20 am »

Thanks for the reply Phil.

"when an aggregation connector is used between Blocks on a BDD, EA creates a Reference Property, which when displayed as a Part in an IDB displays with a dashed border." -- I am in agreement with this and yes I want a dashed bordered reference property.

I am able to create reference properties by an aggregation link between two blocks and in the IBD synchronise elements to see the ref property with dashed border. So with aggregation everything works perfectly.

The problem is if i connect one block to another block (external system) and instead of using aggregation (white diamond) I use the reference connector (straight line only) then i don't see the dashed reference property in the IBD anymore.

For example in the system shown below two reference connectors connect eps to cdhs and flight computer. In EA using these connectors I've found the reference properties are not visible in the IBDs.

https://ptgmedia.pearsoncmg.com/images/chap3_9780321927866/elementLinks/03fig01.jpg

5

General Board / Modelling LANs and VLANS in sysml

« on: August 04, 2021, 01:10:04 am »

Hi All,

In regards to modelling a computer network with subsystems communicating over a LAN and VLAN my idea is to represent each of the LANs/VLANs using an interface blocks that type any ports attached to part properties that represent networked components.

The alternate I guess would be to represent each LAN as a standard block with an in and out port and include an IBD that displays all subsystems connected to both ports to show messages are passed in and out.

I still need to get over the conceptual barrier I'm facing with this one. Please let me know what you think of the above and if you have any anecdotes or know of any exampled networked systems modelled in sysML that would be useful.

Many thanks

Ryan

6

General Board / EA only recognising aggregation and not reference connectors

« on: August 03, 2021, 11:31:27 pm »

Hi all,

In producing my bdds i have noticed that to see a reference property in the IBD I have to use aggregation. It doesn't work with the reference connector without the daimond. In Lenny Delligati's course he avoids aggregation altogether in his descriptions in favour of normal reference connectors.

Is this a nuance of EA or due to my version 13 or am I doing something wrong? Thanks in advance.

Ray

7

General Board / Re: Not able to add ports to nested elements Ultimate 13 edition

« on: August 03, 2021, 05:44:15 pm »

Thank you both for the replies, I will look into how to unlock that security feature.

I was looking at Lenny D's iBD picture figure 4.8 and thinking it must be doable.

8

General Board / Not able to add ports to nested elements Ultimate 13 edition

« on: August 03, 2021, 01:13:13 am »

Hi all,

I've been trying to attach ports to nested elements on my IBDs but I get the message cannot add embedded elements to read only elements.

Has anybody come across this before and know any workarounds?

Many thanks

Ray

9

General Board / Abstract Class in SysML

« on: March 31, 2021, 11:43:25 pm »

In order to have child block value properties with different values than the parent I understand that I must create an Abstract Class as the parent.

Is this possible in SysML and Enterprise Architect and does anybody have any information on how to implement this?

Many thanks

10

General Board / Connecting Instances to Blocks on a BDD

« on: March 19, 2021, 01:07:48 am »

I have a logical system hierarchy broken down into levels of BDDs. These blocks will serve as definitions of type in the architectural mode.

As part of the logical system have have defined some computer racks, these racks contain certain system elements defined elsewhere in the BDDs.

I had originally dropped links in the rack diagram thereby having the block defined in one placed and replicated as being part of this computer rack on another diagram (side point; I used aggregation rather than composition as if you remove the rack you don"t necessarily remove the computers you just put them somewhere else). Now after further consideration I have considered, although the way I have modelled it is acceptable in sysml and offers the advantage of displaying where in the system that block originates from, that they should actually be instances of the block definitions which leads me to the question.

How should these instances be connected on a BDD to a block. The quick linker offers dependency trace and information flow, none of which i want.

The options I believe are;
Aggregation
Composition
Standard Connector

is there a right answer out of the above three options?

Many thanks

Ray

11

General Board / Re: SysML How to define context specific value type properties contained in a proper

« on: March 19, 2021, 12:26:36 am »

Thanks again for the reply,

I should have clarified I already have the value types in the block. I wanted to add the actual values for example part number 123.

I added values types another way so its good to read about the alternative, I created an IBD for the block and dragged in the part properties.

12

General Board / Re: SysML How to define context specific value type properties contained in a proper

« on: March 18, 2021, 09:08:14 am »

Thanks for the reply Phil,

I've now set been able to set the property values within the instances, thank you for the advice, not having the drop down list of the values had caught me out.

So now my next issue is I want value types to be added to a block, I have a feeling it might not be possible but let me know if there is a way.

I am currentlylooking at the possibility of replacing a master BOM spreadsheet with the model, that is to export from the model using the Excel Export tool whenever updates are made to recreate the spreadsheet rather than updating a spreadsheet and updating the model each time which would nullify our system modelling claims of a ‘single source of truth’.

My current model consists of numerous BDDs describing all of the system elements in logical groupings and is predominantly consisting of Blocks

The structure is essentially formed of the top level block associated by aggregation to 6 different blocks representing logical groupings of systems.  Each block contains hidden decomposition and each child diagram contains further decomposition of the system, at some points there is perhaps 7 or 8 levels of decomposition.

I would like to create a spreadsheet with the value fields: level (of decomposition), description and a few other describing features as column headers.

To create this spreadsheet obviously I would need to include these value types for every block.

The inability to add values to the blocks would prevent me using the model to recreate spreadsheet. Is this the correct assumption or is there a way around this?

Thank you to anybody that may have some input on this

13

General Board / Re: SysML How to define context specific value type properties contained in a proper

« on: March 17, 2021, 02:14:21 am »

Hello Peter/Forum,

I am a new member to this forum. I came across this question posed by Peter below which is exactly the same question that I am trying to answer. Apologies for re-igniting the old post but as a solution was never posted I thought it worth bringing back up.

Context:

I have modelled a hierarchal logical breakdown of our system, taking the data from an excel spreadsheet. I am investigating the potential to export the model back to excel rather than updating the spreadsheet and then amending the model. That way our model will be the source of truth.

Current issue:

I have created a block to type the element. I created 3 generalisations, initially I had created three blocks before realising they should have been instances. I was able to get the value compartment within the blocks to display the value properties using the 'structural elements' and 'features and compartment visibility' however I haven't been able to display them in the instances, only nesting the properties so far. The values checkbox within features and compartments that is visible in for the blocks is not there for the instances, i see 8 checkboxes instead of 9.

As well as viewing those value properties I want to assign values to them such as product codes, description etc. Once I have done this I can explore the possibilities with exports to excel.

Any help with assigning values to the instances would be highly appreciated