SysML Physical Interface Modeling with Custom Whitebox ICD

[@mauricejoy3432]

How would you bring in the cable to the the IBD for the system? The cable would also have the connectors/interfaces on it. If you didn't need to go to the pin level

[@BruceDouglass]

Nice. I do the same thing but you flow properties (which can also be typed by blocks) rather than reference properties.

[@brianMoberley]

That is a very good point Bruce! Thanks for the comment!

[@nicholaschastain7445]

cannot populate the metachain like your video. I wish you would redo this with a step-by-step.

[@brianMoberley]

Thanks for the feedback Nicholas. Sorry you weren’t able to get the Metachain working. I will likely remove this video soon and redo with a different approach. Is there a certain point in the Metachain that you rate having a hard time recreating?

[@taimoorahmed_507]

Thanks Brian! This was very helpful in developing a custom ICD table. Having the ability to look at one connector end at a time does wonders for me! Haha.

[@brianMoberley]

Hi Taimoor, I’m glad it was helpful! It is definitely very useful to parse out the connector ends. Thanks for checking it out!

[@brianMoberley]

Though this is one option for modeling pins, after much consideration, I’d like to recommend using nested ports instead of Reference Properties. See this video as an example: kzbin.info/www/bejne/bYOkmGuVhqefqpY

[@idontknow1134]

Good job

[@candyreid59]

This is great. Thank you

[@brianMoberley]

You are very welcome, Candy. One thing to add, instead of using Reference Properties for the pins, it will likely make the most sense to simply use Nested Ports where each nested port will represent a pin of a connector. Thanks for watching!

[@gengistr4566]

Thanks for the video. There isn't much information on MD/MBSE interfaces around. your video is worthy although the title deserves much more content. Do you have a more basic video explaining basics of interfaces, like the difference between connections between ports and between references/properties of ports? For example, for simulation what actually connects easily data is the properties connectors, but they are hidden if we show the ports in the reduced version (small square) which is the most convenient when you have many ports and connections. Why or how is useful the connector between ports? MD has association blocks, but not know if this apply for this or how to apply them!

[@brianMoberley]

Gengis, You have a lot of great questions! I do have another video that discusses interfaces titles "Ports | Pins | Interfaces | and more, however, it may not be quite as basic as you are asking for. I can definitely do a video on the topics you've mentioned though! To answer your question about the usefulness of a connector between ports, they are very useful to show that there is an interface that acts as a point of exchange for data, matter, or energy. They are very useful for querying to create ICDs and also very useful for simulations where Signals, Values, or Other Objects that represent Data/Matter/Energy can be sent across the interface to then be acted on by other parts of a system. As far as Association Blocks is concerned, I still have my questions about the usefulness of them. I personally don't like they very much but they can be considered the "definition" of a connector, whereas the connector can be considered the "usage" of the Association Block. I personally don't think they are necessary. If you want to try using setting one up, however, you have to start at a BDD where you have the two Blocks that will have a connector places between the usages of the blocks (in the IBD), click on Association Block from the pallet, then click from one block to the next to create the association block. Then, once you get into the IBD that is one level higher than the two blocks you connected the Association block to, you'll right click on a Connector that goes between the part properties or proxy ports, and go to "Association," which is where you can select the Association Block that you created in the BDD. The connector will then have a "type" with the name of the Associaiton Block displayed after a colon ":" At that point, however, I'm not really sure that it helps you that much! :)

[@jamessaari4785]

You should note that the order of connector attachment affects which is A/1 and B/2... the three connectors in IBD need to be attached in the same order (left-to-right or right-to-left) to make the tables make sense.

[@brianMoberley]

That is a great point, James!

[@fhepeople]

Do you have any videos covering logical interfaces?

[@brianMoberley]

Ryan, I don’t have any videos that specifically demonstrate logical interfaces but I do have the video “Ports | Pins | Interfaces and more that is geared more toward logical interfaces. Now that you mention it, it would be good to have a video specifically on the topic of Logical Interfaces. Do you have any questions specifically in regard to Logical Interfaces or just wanting to see the contrast between logical and physical?

[@fhepeople]

@@brianMoberley I believe I have seen that one on Ports, Pins and Interface. I am trying to model an interface, where I have all the meta-information on the physical characteristics (busses, bits, etc.) and also the actual data types being represented. I think I could model both, but not at the same time. I want to know how to tie the physical and logical representation of an interface together. I've seen approaches which use connectors and item flows to represent the physical side, and interfaces to represent the logical side, but how do you connect the two? This is a tough problem, I know, so thanks in advance if you can think of anything that helps.

[@fhepeople]

Ahh, I took a second look at the Ports/Pins/Interfaces video, and it had a lot of cool stuff! I think the technique of reference properties on interface blocks sounds promising for my problem. You mentioned videos by someone named Mike Vinarchek (?) covered that idea? Do you have a link to them?

[@brianMoberley]

Ryan, if you look up the channel System Architecture Guild, that is Michael Vinarcik’s channel. He has a lot of great content as well.

[@fhepeople]

@@brianMoberley Yeah, I was able to pull it up, and it looks like it has good content. Thanks!