Відео

I actually completely agree with you. We are working more robust examples to explain other methods to design logical and physical breakdowns and explain the pro/cons of each method. That video will be released in a month or two.

@@CameoMagic That sounds great. You have some of the best, most focused, and most approachable content I've seen, so please don't take this as any sort of critique about your examples. Just trying to wrap my head around what to do with that knowledge! 😃 Thanks again for this one.

check our website for more info at www.cameomagic.com We have paid in person courses, paid consulting, and exam prep materials. Right now we do not have any paid online courses as we are trying to keep as much of our content free so people can access the resources without jumping through hoops. We did create a free playlist for learning which covers most of the SysML diagram types: ua-cam.com/video/23d31BHjgxs/v-deo.html

Absolutly, you would typically tie the value together between diagrams using a value property. In the parametric diagram, you can connect the constraint parameter to the value property using a binding connector. In the Activity diagram, you can manipulate the value property with an opaque action. Note: Ensure you run the simulation with context so the Activity diagram has access to the value property, which is connected to the block (the context).

@@CameoMagic Appreciate the answer then by doing what you recommended, am I able to show an output (String) in the Activity parameter nodes from an input? Was that shown in a tutorial?

Create a package for the templates

What do we want system do and what are we trying to build

yes, the benefit of it creating the redefined value property just saves you to manual time to select redefine. If you have multiple rollup patterns they should be independent of one another but I'm not thinking of a case where this would be the best implementation. The rollup pattern will be applied to all blocks below the subject of the applied rollup pattern. So, if you have applied a mass rollup to subsystem A as the subject. And you applied a separate mass rollup pattern to subsystem B. and then you were to run a simulation at the system level with subsystem A & B then you would be able to see the mass of subsystem A & B separately. You would not get the total mass of the system though. So, wouldn't it just make more sense to remove the rollup patterns at the subsystem level and apply a single rollup pattern at the System level so it would rollup the totals for subsystem A and B into a system total mass value? I'm not sure I follow your last paragraph. I will revert to restating that it rolls up the value properties from the part properties below it recursively. The miss rollup will take the sum of the children's mass. The child's mass is calculated based on the child's children's summed mass. And loop continues until you get to your smallest element.

A metachain can be made for this. In hindsight, we should've added that to this example. Pro: Scalable for mechanical, electrical, etc. aspects. Fairly easy to implement. Con: Metachain more involved. Another alternative is that you have a completely different breakdown that is purely physical and not logical and then map elements from one breakdown to another with a relationship like a(n) abstraction or dependency relationship. Pro: No complex metachain, arguably more straightforward. Con: Must make entire new decomposition (longer to implement). Another alternative is that you have a relationship between the physical block and the logical element (via mount relationship potentially). Pro: Fairly easy to implement. Con: Metachain involved (not terribly difficult), not quite as scalable (arguable) I'm sure there's other alternatives as well. I think either way you model it, you will have the trade space between doing a lot more modeling with less metachains necessary or doing less modeling with a more complex metachain required.

@CameoMagic would love a video going over some of this.

Nice, good method. I like the idea of starting from one part and then working your way outward. I absolutely understand the issues with the direction of the connector.

I could've used either the Properties or Attributes tabs; they are VERY similar and ultimately refers to the same element. The thing that I've noticed is that the Properties tab organizes results by Property type (Part Property, Value Property, Constraint Property, etc.) The Attributes tab organizes results by how the attribute has been added to the element (Owned, Inherited, etc.) So making changes to either will create the same elements/relationships in the model. The difference is the order in which the elements they are presented.

The variable simtime() can be called and then utilized.

please do

Go for it! Glad you liked it!

"run" means "execute" in simulation. When you "run" with the context of a block you will run all of the things which are connected to that block. A block can have a classifying behavior which is a behavioral diagram which is run when the block is run. Therefore when you run the block, you will startup the classifier behavior (i.e. Activity Diagram, Sequence Diagram, State Machine Diagram). The classifying behavior can then kickoff other behaviors. Parametric diagrams are a structural diagram which is behaviorless. Therefore the constraints which are captured with a constraint block will be global (always true) for whatever behavior the system block does. That's why we typically have laws of physics and such as a constraint on our parametric diagram (laws of physics are always true). Hopefully this helps. I'm not sure I answered your question.

Note: as you watch the videos you will see there are actually 2 play/"run" buttons. The first calculates the structural parametric constraints and spits out the answer, the second starts the behavior. The behavior can modify the inputs and then change the parametric. (i.e. the total mass of a system will decrease over time as the system uses fuel)

Yes, unfortunately, we are not distributing the .mdzip files at this time. We apologize for the inconvenience. We are glad you enjoyed the video and hope you continue to watch & share the content.

Run the simulation with Matlab as the language of the solver. This will allow you to select which variables are inputs and outputs.

ua-cam.com/video/8aSKaGdKIjw/v-deo.htmlsi=7Ie6HZq_bcpOIJig This video may be helpful to you.

Yeah, extract is finicky unfortunately. Try just selecting the behavioral actions (the send signal elements only) and not the logical nodes (do not select initial node or fork) and see if that works for you.

@@CameoMagic Got it thank you!

@@CameoMagic Another question: Here you have used send and accepts signal actions. In my model I have some physical flows (e.g. Air, water, etc.), those are not signals but blocks. Should I convert them to signals and use the same method or how should I go forward with item flows that are blocks?

@@mayureshbhide4692 You have a lot of different options to pass data from one place to another. This video goes over some of those alternatives: ua-cam.com/video/IsrGBhvWsf8/v-deo.html&t It's hard for me to guide you what to do without seeing your entire model but I would think that keeping the Air, Water, etc as blocks may be the best path forward. Best practices would be to remain consistent with the other models you are integrating in with, and try to model using the most clear/understandable method for people who have not seen the model. If your team is going to say, "water flow is not a signal; a discrete or some software sending a message is a signal" then may be keep it as a block. Defining what terms such as "signal" means to your team is important as SysML leaves it up to the modeler. That being said, send signal actions and Activity Parmenter nodes do work differently so understanding the differences would be helpful before deciding a method for your entire project.

In Cameo 2021, I do not know a way to toggle the legend adornment. However, I have not really had this problem. I have had issues with the validation checker slowing me down. You can go into Environment Options / Active Validation / Active Validation Period and then make it something really large like 30sec so that it doesn't validate upon opening the diagram. I would check that this isn't the thing slowing you down. Additionally, I would look into Environment Options / Memory Settings and changing your Max Heap Size and Thread Stack Size. I've got mine set to 6000 and 1024 respectively. If you really think it's graphics related then check some of the other Environment Options such as Diagram / Graphics Antialiasing and Diagram / Text Antialiasing. Try setting these to false and you may be able to sacrifice graphics quality for speed.

"A Viewpoint is a specification of the conventions and rules for constructing and using a view for the purpose of addressing a set of stakeholder concerns. The languages and methods for specifying a view may reference languages and methods in another viewpoint. They specify the elements expected to be represented in the view, and may be formally or informally defined. For example, the security viewpoint may require the security requirements, security functional and physical architecture, and security test cases." -SysML Book You can look at figure B27 on page 183 of the SysML book for a pictural example. In simple terms. A "view" is another word for diagram. "Viewpoint" is not a diagram; it is an element in the model. The viewpoint has attributes to fill out such as stakeholders, concerns, purpose, etc. You can think of it like a requirement element where your requirement has a text field to input data. The view is connected to the viewpoint with a conform relationship. Hope this helps.

Simulation toolkit plugin.

@@CameoMagic thanks, i’m newbie’s mbse. Can we install this plugin through Magic Systems of Systems Architect (license Academic) ? I tried to install but it says version incompatible error.

@@mr2tot I'm not sure I understand your question entirely to be honest when you mentioned "Magic Systems of System Architect". You can Import the plugin by opening Cameo, going to Help/Resource/Plugin Manager, and then selecting the "Import" button. You can successfully pair any version of Cameo Systems Modeler or Cameo Enterprise Architecture to Cameo Simulation Toolkit plugin. You will need to ensure the version of the plugin matches the version of Cameo you are running (i.e. If you're running "Cameo Enterprise Architecture 2021x" then "Cameo Simulation Toolkit" version 2021x Refresh2 will be compatible)

In the video, we're using Cameo Enterprise Architecture. Note: Cameo Enterprise Architecture, Cameo Systems Modeler, and MagicDraw are all fundamentally the same tool.

There's two buttons (icons) right beneath the word "Containment" when looking at your containment tree. If you hover your mouse over the icon it shows its label: "Collapse All" and "Collapse Selected Recursively". Both of these icons will collapse the containment tree. I suspect that you are accidently hitting these buttons. When you change from project to project the containment tree will remain how you left it, or that's how it's supposed to work. If you are still having issues I would suspect a Cameo bug and I would try closing Cameo and reopening it. Hope this helps.

FWI I have not seen this behavior, and I usually have several models open simultaneously. (versions: 19.0, 2021x, and 2022x)

There's not at this point. Our most comprehensive SysML walkthrough to date is this one: ua-cam.com/video/dQqNg0EE7L4/v-deo.html

Cameo Systems Modeler 2021x

Here it is: ua-cam.com/video/IsrGBhvWsf8/v-deo.html

The relationship created was an association which is a directionless relationship which creates 2 reference properties where both ends reference each other. That's why there's no diamond on one side or arrow. At 4:03 In the containment tree, Subsystem A has a reference property "power Block: Power Block". Additionally, Power Block has a reference property "subsystem A: Subsystem A". When you say "instantiated" I'm assuming you mean that you're not seeing the row for the reference properties at all when running the simulation. If this is the case, then select the gear icon within your simulation window and then toggle "Show Reference Properties" to on.

@@CameoMagic Yes that's what I meant. Toggle "Show Reference Properties" to on did the trick. Thank you so so much! Liked and Subbed!

Here's a tutorial on how to hyperlink: ua-cam.com/video/cs7aCP-v0Z4/v-deo.html

Here's another video on connector and pinout modeling: ua-cam.com/video/pBYLmPnG_kY/v-deo.html Hopefully, this will help because we haven't posted an exact creation video at this time.

and why are there two modes? when to use each of them?😣☺️

We're going to need a video to explain that one because the answer is "it depends". I would refer to your methodologies guidance. Typically, a methodology will dictate either allocations between elements of definition or between elements of usage. The entire model will follow that guidance (i.e. you likely wouldn't do both in a model).

@@CameoMagic oh thank you for your kindly reply and I'll pay more attention to it. ☺