![Skygazer Consulting](/img/default-banner.jpg)
- Видео 6
- Просмотров 179 286
Skygazer Consulting
Добавлен 18 окт 2014
Tips and techniques for modeling systems in SysML
Example of Conceptual Modeling using SysML
NOTE: twice in the "requirements" section of the video I referred to "composition" when I meant to say "containment". Requirements can't be composed, only contained. Also, the «deriveReqt» relationships are shown in the wrong direction. Shame on me!
This is an absurdly simple example of conceptual level modeling using a SysML tool (Astah SysML 1.3). The focus of conceptual modeling is building up a solid set of requirements on which to base the initial system design. This example includes requirements, use case, domain/context, and activity (functional flow) modeling.
This is an absurdly simple example of conceptual level modeling using a SysML tool (Astah SysML 1.3). The focus of conceptual modeling is building up a solid set of requirements on which to base the initial system design. This example includes requirements, use case, domain/context, and activity (functional flow) modeling.
Просмотров: 21 697
Видео
SysML Diagram Types Quickstart
Просмотров 22 тыс.9 лет назад
The number of different SysML diagram types can be very confusing when someone is just getting started, or when someone is coming from a "traditional" systems engineering background. In this video, I explain how most "traditional" systems engineering can be done by only learning 3 different types of SysML diagrams.
Importing .txt Questions Into Blackboard Quizzes
Просмотров 3,1 тыс.9 лет назад
How to import the quiz .txt files into the UCSD version of Blackboard, which appears to be version 9.1.82223
Parametric Modeling in MD
Просмотров 4,9 тыс.9 лет назад
Short video on building simple parametric models in MagicDraw, including Value Properties and use of Value Type libraries.
Putting an ItemProperty on a Connector in MagicDraw
Просмотров 2,1 тыс.9 лет назад
ItemProperties are "parts that flow", typed by blocks like any other part should be. Getting them set up correctly in MagicDraw isn't obvious, but here is the way I do it.
The Four Pillars of SysML (in 30 minutes)
Просмотров 126 тыс.9 лет назад
This video presentation covers the basic concepts and notations of the Systems Modeling Language (SysML) in under an hour. I developed the original 4 pillars charts around 2006... since then they have been incorporated into a surprising variety of presentations, white papers, and textbooks. I recently decided to update the graphics and provide my own commentary in a more accessible format.
Amazing.. at 2x speed ! The clarity and punch 🎉
Good explanations. I enjoyed this quick video also on the topic: ruclips.net/video/8eIncaaZF-U/видео.html
One nice thing about getting used to modeling and the tool, is that you get to where you can use the tool to interactively capture things and relationships and progressively develop them (yourself and with others). That is, you get to where _you can brainstorm with the language and tool._ This is a way that the model becomes a _means_ to developing systems rather than the _end_ of some other development process. It's handy to keep a template with the common packages and skeletal diagrams already established to be the "envelope" your "write on the back of" when you're sketching a concept.
Grest demonstration! I too am glad you did a socio-process model rather than an engineered device. Moving from domain engineering into systems engineering means you need to keep people and "people things" in mind.
Low Talker
Will you be putting out any new videos?
Good overview of the SysML diagrams. It's very important to explain to new modelers when to use which diagram. Well done!
Very clear examples of the SysML diagrams with examples. Thanks.
Thanks, Rick. I prefer SysML because it simplifies things. Thanks.
Thank you!
I have one question, at 21:23 could you use a control flow instead of an object flow between both prepare menu and shopping list?
Perferct explanation, i`ll dig into it.
Nice pace man!. Other videos are basically just reciting the official docs where they mention every type of connection etc. At least here you give a good overview of what most people will want to use.
I like the fact that you use a non-engineering example in this video. Sometimes even engineers can gain valuable insight into system modeling by looking at it outside their typical work-day domain.
Is there a way to create use case diagram and relate to other diagrams in the model?
great video - thanks for sharing your knowledge
Why Sysml or OPM when we have Modelica ?
Great Video
I'm stupefied that this is the first I'm hearing of SysML.
I like it !
Excellent presentation, Rick -- thank you. If you're up to it, it'd be helpful to see a similar presentation on OPM (Object Process Methodology), which takes different approach in some ways, by including processes (not only objects). Personally, for a complex system, SysML helps remove ambiguity and complexity, among other benefits, and I like it. I have yet to apply OPM, and I'm curious as to how they will differ. Thank you so much.
Setting Systems Engineering back more than 50 years. As a Systems Engineer practicing for 36 years I am dumbfounded. Apparently Object Oriented S/W programming needs have now driven a redesign of Systems Engineering practices so that the coders' job can be done without the need to think. If SysML turns out anything like Object Oriented Code, the documentation generated will be nearly indecipherable and scattered willy nilly so that putting it into an understandable description of what the system does will take longer than the design required in the first place. I do appreciate the explanation however, it is well presented. I just fail to see the utility in SysML other than placating the needs of OO programmers. It certainly doesn't do much to help understand what a system is actually supposed to be doing as far as I can see.
Thank you so much!
Can you please share the presentation used for the explanation.
Play it at 2x speed and it's only 15 minutes :-)
Excellent illustration of the four pillars!
Excellent tutorial on SysML. Well worth the time!
This is excellent. The process of navigating through the MagicDraw/Cameo Systems Modeler workflow can be labyrinthine.
perfect: quick yet comprehensive. good ramp up, especially for software engineers who already familiar with UML. In terms of 4 pillars, it is subjectively a very definition of any software or system architecture
This was a fantastic example, thank you.
Fantastic beginners insight to some elements of SysML. Thank you.
Great explanation and demonstration! Thank you very much!
A program that turns mathematical principles into flowcharts. Is the friction block considering the coefficient of friction and can you see all the mathematical equations use across all the blocks?
Hands down the best video I have found on the mindset and approach to MBSE in SysML.
Thank you this was very helpful
Very well done. Thanks. Everytime I question myself on something re: SysML, I always seem to keep coming back to your video to continually refresh the fundamentals of the 4 pillars. I appreciate you sharing your knowledge. Cheers.
More than the details of the example, I was interested in the ontology used and which items in which packages can be reused in other packages.
Fantastic tutorial wish you had more content available!
¿Cómo obtengo las plantillas de sysml para vice 2010?
This was an excellent presentation.
Your videos are fantastic, thank you!
Thanks! This was a nice first view on SysML
It makes it a bit more clear to me!
I work as a CAD/CAM/CAE person and no matter how hard I try, I'm completely lost when it comes to understanding something like SysML. This presentation is well paced and thought out and yet I'm completely lost. Funny that one vender of SysML diagramming tools is called "no magic" well to me...it is magic! Same goes for requirements management, it gives me the creeps--though I understand it's important!!!
I agree. I do most of my work in CAD and I don't understand the point of SysML and tools like Modelio. Is it a brain mapping tool? What does it output? It isn't equipped for extensive simulations so I can't use it to model vehicles very well. Right now I'm more tempted to put out the money for a dedicated vehicle modeling program.
@@ben-2368 I'm a software guy and we make plenty of UML diagrams (UML is the father of SysML etc. etc.) and most of them can infact be used to produce code, both by hand (the diagrams define structure and behaviour of programs) or automatically (diagram to code and vice versa) but for SysML, I dunno man. I don't see why I should use SysML over UML, UML is (at least to me) even more readable than this. Block diagrams just feel like an even more abstract version of a class diagram, which in itself differs in how you implement it based on your language.. This just seems too abstract to me.. I mean abstractions are nice, but this is as abstract as it gets and almost obscures things.. But oh well. Maybe I'm just missing the entire point of it
SysML is probably not for you. It was developed to provide a formal language for describing system level needs, properties, top level analyses, interfaces and requirements, as opposed to relying solely on textual specifications. Some of my students have never had to develop system level specifications, and are much more comfortable with more concrete engineering concepts. I just hope you recognize that the system specifications need to come from somewhere, and it might be a good idea to model them before the detail design engineers like yourself are forced to comply with them.