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.
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.
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.
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.
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.
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.
Fantastic beginners insight to some elements of SysML. Thank you.
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.
This was a fantastic example, 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?