Modeling Information Flow

Discussions about systems engineering product SysML functionalities

Moderator: Moderators

Modeling Information Flow

Postby Stern » Mon Feb 05, 2018 2:52 pm


I have a question regarding methodology- this is not a technical question. If it is not appropriate I apologize!

When generating a model for something such as an electronic device, where sub components may send many signals to each other, what is the proper way to capture the flow of information/signals?

In a scenario where a subcomponent outputs up to 6 different signals, and there are multiple subcomponents, generating ports and typing them with a flow specification gets to be cumbersome and messy. Is this the only correct way? Would it also be correct to instead create signal properties, and use the 'Conveyed Information' capability to show flow of all 6 as a list?

Again, please ignore if this is outside the scope of what you guys are here to help with!

Thank you!
Forum Newbie
Forum Newbie
Posts: 17
Posts Rating:0
Joined: Thu Sep 21, 2017 8:35 am

Re: Modeling Information Flow

Postby » Tue Feb 06, 2018 10:03 am


Currently, Cameo Systems Modeler (or MagicDraw + SysML plugin) supports SysML 1.4 specification (and SysML 1.5 in the upcoming 19.0 version). There are rules/constraints how to define interfaces and connections between them in order to have a correct model (simulatable, without validation errors, working ICD tables etc.). I'd recommend you to look at the "SysML 1.3 Interfaces Modeling" sample (which is bundled with the product and available under SysML Samples group). It provides guidelines for the interface modeling with SysML. Also, you could take a look at our documentation: ... sing+ports

Talking about other methods: yes it may be applied another method, however, it depends on many factors, e.g. what is abstraction level of your system, do you want to simulate your model. Your mentioned way of using the 'Conveyed Information' capability may be possible too but, currently, it's not supported (or is not convenient) out of the box. If you would like to use custom methodology, I would recommend you to contact our custom services:

Also, one remark, since the SysML 1.3 version, Flow Specification is deprecated, instead, Interface Block should be used.

Have a nice day,
Donatas Mazeika
Forum Expert
Forum Expert
Posts: 121
Posts Rating:17
Joined: Tue Apr 21, 2015 12:30 am

Return to SysML

Who is online

Users browsing this forum: No registered users and 1 guest