Databus Modelling and IBDs

[Ryan]

Modelling the interfaces, connectivity and passage of information is more challenging than modelling mechanical systems. If anybody has references or examples of how to approach this task I would be really grateful. I have Lenny Delligatti's book and the practical guide to SYSML. If anybody here has expereince modelling complex networks I would love to get in touch.

Kind regards

Ryan

[Shames, Peter M (US 312B)]

Hi Ryan,

 

I agree that modeling components and interfaces re how information is passed among them is a challenging topic.  I suggest that you take a look at the attached paper and presentation, authored by Marc Sarrel, Sandy Friedenthal, and Peter Shames.  There is a careful treatment of an approach for modeling systems, components, connectivity, interfaces, protocol stacks, protocol behaviors, and the data objects that get transmitted. 

 

It can be applied to individual components and to systems of systems.  Many aspects of this are to be addressed in the SysML revisions now being worked.

 

If you wish you can reach out to me separately about some other papers that use this method to model complex, networked, systems.

 

Regards, Peter

--
--
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/2b2f692a-eb5d-4ead-a0d6-c9e274ee8254n%40googlegroups.com.

[Darren Spooner]

I would also be interested in knowing.

To view this discussion on the web visit https://groups.google.com/d/msgid/sysmlforum/C99856B0-624C-4DFE-B5DF-A606FDDFC1DA%40jpl.nasa.gov.

[Keith Siders]

I've been following that pattern to update MIL-STD-1553...

To view this discussion on the web visit https://groups.google.com/d/msgid/sysmlforum/C99856B0-624C-4DFE-B5DF-A606FDDFC1DA%40jpl.nasa.gov.

[Walter Roscello]

I have previously addressed this issue by using a proxy port to represent the interface as a whole, and using nested ports to define the different aspects of the interface.  So, a data interface might have nested ports to define the physical connection, the protocol in use, and the data being exchanged.  This is essentially what is being shown in Figure 3 of the paper provided above.

This should also allow you to reuse standard definitions from a library, such as for a RJ-45 physical connection, while limiting the application-specific definition to the data definitions.

[Ryan]

Peter,

Thank you for the links, the layered interface approach has a lot of relevance to my work. 

It got me thinking in terms of the OSI model again which I'm familiar with from taking a CCNA course a couples of years ago but do need to revisit topics.

Thank you for offering to reach out, I will be happy to connect with you again.

Many thanks

Ryan