3:35
2024-12-16 13:15:46
41:29
2024-12-16 13:22:05
48:13
2024-12-16 13:27:55
13:32
2024-12-16 15:19:39
16:25
2024-12-16 15:19:40
9:39:05
2024-12-16 16:37:54
12:47:46
2024-12-16 16:38:02
19:48
2024-12-18 11:57:41
Visit the Ai Assisteed MBSE course recordings page
WEBVTT
-->
So now I'm going to do what I just suggested a minute ago, which is I'm going to create
-->
a package inside conceptual model called domain model.
-->
So that's create element package, call it domain model.
-->
And now I'm going to create a BDD inside there, and I'm going to leave it called
-->
domain model.
-->
And then I'm going to go to my slides and what I have is an electron gun, an imaging
-->
system, a vacuum system, detector, all that, right?
-->
So how do I get back to my, how do I get back to my, so I don't know if you all
-->
know how to use the sticky button in Cameo, but I'll show you how to do that.
-->
Let's see, Elena, are you caught up now or not yet?
-->
I think so.
-->
I'm good to go.
-->
Okay.
-->
So if you've never used the sticky button in Cameo, it is this little icon here.
-->
And you use it when you have to create a whole bunch of elements that are all the
-->
same type.
-->
So I think I need to create like seven or eight blocks here.
-->
So I'm going to click the sticky button, click on block, and go one, two, three,
-->
four, five, six, seven, eight.
-->
I don't know if that's exactly the right number, but then I'm going to turn
-->
the sticky button off and I'm going to start naming these.
-->
I'm going to show you a little driving trick with Cameo, and that is this little
-->
make preferred size button here.
-->
Yeah, to save you just hit this little floppy disk icon.
-->
But I think we'll be done with this diagram in five minutes.
-->
So what we're doing now is we're just copying the BDD out of my PowerPoint slides.
-->
And we're going to use composition, directed composition, to map all these
-->
together, connect them all together.
-->
I can use the sticky button for that too, so I can make all my directed
-->
composition relationships that way.
-->
And then I'm going to name all these.
-->
So electronic imaging system, vacuum system.
-->
Then I made one block too many, so I'm going to delete my extra one.
-->
And then I'm going to use this quick layout button, lay it out like that.
-->
And let me just check how everybody's doing.
-->
Looks like we're doing good.
-->
And the last thing we'll do before lunch.
-->
Is we're going to create a glossary.
-->
And we do that by right clicking on domain model.
-->
Go to create diagram.
-->
Under other diagrams, there's something called the glossary table.
-->
And what we do with this glossary table.
-->
Is we're just going to take all of these blocks.
-->
Drag them onto the glossary table.
-->
And now we can put in the glossary descriptions.
-->
So that's actually our first lab.
-->
And we finished it a minute before lunchtime.
-->
So I think we're good.
-->
Just drag them over from the containment tree into the empty space on the diagram.
-->
Oh, just into here.
-->
And then just select the elements to table.
-->
I think you're doing things and I'm staring at my computer and I'm not looking at what you're doing.
-->
No problem.
-->
Just need a little heads up that you're about to do something and then I can stop looking at mine and then look at what you're doing.
-->
We will calibrate to this as we go on.
-->
Thank you so much.
-->
My goal was to get us through this by lunchtime.
-->
So it is now lunchtime.
-->
Right, right to the minute, Maria.
-->
And so we'll see you back here at one thirty.
-->
Thank you.
-->
Yep.
-->
I think we're good, Maria.
-->
It ain't broke.
-->
Don't fix it.
-->
No, I think we are.
-->
We're off and running and actually got through the first lab before lunch.
-->
Right.
-->
All right.
-->
See you in an hour.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Thank you.
-->
Hello.
-->
Welcome back.
-->
I'm migrating to a new target data center for my connection.
-->
All right.
-->
Is that something that's in progress or are you done doing that?
-->
It's doing it, but I don't think it's going to slow us down.
-->
It's been about a minute and a half for the connects.
-->
It's not much faster.
-->
I heard something about that.
-->
Yeah.
-->
A pop-up came up and said that I could get a better connection if I migrated.
-->
I put yes about a minute and a half ago.
-->
I'm off cancel.
-->
I'm fine, I'll just use that.
-->
Yeah.
-->
Thanks.
-->
Okay.
-->
So, Elena and Daniel, are you guys back?
-->
It's a yes from Daniel.
-->
Okay.
-->
Well, while we are waiting, let me once again ask for some feedback.
-->
How's it going?
-->
How's everybody doing?
-->
Are we still on a good pace?
-->
Too fast?
-->
Too slow?
-->
Too deep?
-->
Too shallow?
-->
Where are we at?
-->
I'm not sure what you said, Daniel.
-->
Was it all good?
-->
Yeah.
-->
Okay.
-->
Your voice kind of fades out a little bit when you're talking, but I'm going
-->
to take that as an all good.
-->
Mark, you good?
-->
Yeah.
-->
I'm fine.
-->
Although I ran out of coffee, so I'm a bit of a pickle over here, but otherwise
-->
one is good.
-->
Yeah.
-->
If we need to pause for people, that's great.
-->
I've had my moments where I get behind, so I'm fine.
-->
Yeah.
-->
Okay.
-->
I'm trying to keep everybody synced up the best I can.
-->
Yeah.
-->
My impression is that the two of you from Raytheon probably have more hands-on
-->
cameo experience than Elena does, so I'm trying to go at a pace where she can
-->
keep up and you guys don't get frustrated waiting.
-->
So if I'm not doing a good job at that, let me know.
-->
But hopefully it goes okay.
-->
I've been teaching for quite a large number of years, so I feel like I know how to
-->
handle it, but if I need to get feedback from you, don't hesitate.
-->
It's also nice to see what they're struggling with, because other people are
-->
having the same problem, so I'm like, oh yeah, I do have to explain what this
-->
little weird-looking bundle button up here means, and they don't just know it,
-->
so it's good to see what the challenges are.
-->
Yeah, cameo is a piece of software that has like 18 million features in it,
-->
and I certainly don't know all of them.
-->
I know the ones that I use all the time, which is quite a few of them,
-->
but you know, it's not all of them, right?
-->
Yeah, also there's a lot of user interface inconsistencies in cameo.
-->
You can sort of see that parts of it were developed by different teams at different
-->
periods of time, because there'll be sections of it that have sort of the same
-->
user interface idiosyncrasies to them.
-->
And they clearly didn't write any use cases when they built cameo.
-->
They didn't use like EML and use cases to design it, because one of the
-->
use cases is that features that are really hard to read when you try and document
-->
how they work in use cases, they read completely ridiculous.
-->
And so my favorite one is the standard and expert mode toggle, where it's in
-->
expert mode when it says standard, and it's in standard mode when it says expert.
-->
And the documentation says click on this button that's not there, or menu item that's
-->
not there, because you're not in super expert mode.
-->
Yeah, I taught a live in-person class last week, and there was one guy in the
-->
class who kept thinking he's in expert mode because it says expert on a
-->
screen. Why would anyone ever think that? I don't know, but you know.
-->
It's crazy.
-->
Yeah, I taught with Sparks for many, many years before switching over to cameo.
-->
And for UML, Sparks pretty much I think dominated the industry, but with
-->
SysML cameo kind of took over.
-->
Yeah, which was strange. It fell apart.
-->
I'm sorry, it was free, but we probably spent more money, you know, fixing
-->
things.
-->
Debugging it, yeah.
-->
Elena, are you back yet?
-->
Elena is not back, but we're seven minutes over time, so.
-->
Nothing you can say.
-->
Okay, so I'm going to go back to PowerPoint for a few minutes, and then
-->
we'll do some more cameo modeling in a little bit.
-->
I'm just going to put a note in the chat for Elena to say please let us
-->
know when you're back.
-->
All right, so, by the way, these domain objects didn't come out of thin
-->
air, they came out of me asking ChatGPT, alias Dr. Nano, what the
-->
domain objects were, and I can kind of show you what his response looked
-->
like.
-->
So, basically, when, this was very, very early in my chat session
-->
with ChatGPT, and by the way, I exported it to Word somewhere about
-->
when I was writing this chapter, and my conversation was over 300 pages
-->
long, but it kind of started here, which as I just said, gave me a set
-->
of domain objects for scanning electron microscope and their
-->
definitions, and it kind of gave me those like that, it gave me the
-->
rest of them, and it kind of looked like this, and then I sort of
-->
had a detour into asking it to write some use cases, and we cover
-->
the use cases in the use case chapter, not here, but this was pretty
-->
early in the book project when I was still getting to know Tim, my
-->
co-author, and we were kind of on a Zoom call with Tim, or maybe
-->
it was email, but we were talking about how basically we were
-->
switching back and forth between doing the domain model and some
-->
different views of the system, and so one thing I had it do was
-->
write a couple of use case narratives and look at the text of
-->
those, and Tim said to me, oh, you're following the zigzag
-->
pattern, and I said, zigzag pattern, what's that, and it turned
-->
out that Tim had written a book on his process, which is called
-->
SysMod, and he had actually documented this going back and
-->
forth between the requirements and the architecture as a zigzag
-->
sort of thing, and I had just done the zigzag pattern kind of
-->
intuitively because that's always how I work, but then he gave it
-->
a zigzag pattern, and so we decided to put that in the book,
-->
and I thought it was a very insightful thing that he had done
-->
is to recognize that you zigzag back and forth in between
-->
different views of a system as you develop it, and it really
-->
helps you discover things. He was using it to discover
-->
requirements, which we'll get to in the next slide deck, but
-->
I used it in particular to get some information out of the
-->
use cases and get some information out of subsystem
-->
decompositions, and in a sense, we're kind of cheating
-->
a little bit because we really haven't done a subsystem
-->
architecture yet, but even though we hadn't done the
-->
subsystem architecture, we kind of cheat and have AI take
-->
a guess at the subsystem architecture even though it
-->
wasn't final, and that helped to discover some more
-->
domain objects. So when we had Dr. Nanow start writing
-->
use cases, he came up with some interesting nouns like
-->
he had pre-processing tasks, image enhancement techniques,
-->
ROI, which is region of instruments, operator settings,
-->
instrument settings, and so we started adding some of
-->
those to the domain model, and one of the nice things
-->
about how AI works is you can almost always ask it
-->
for more detail on anything that you're doing, and it
-->
has kind of a habit of presenting things to you,
-->
maybe 10 items at a time or maybe 20 items at a
-->
time, but it'll tend to not give you 50 items at a
-->
time or 200 items at a time because people don't work
-->
that way and they can't handle that much complexity or
-->
that much detail all at once. So I asked it to define
-->
things like what's a pre-processing task and what's
-->
an image enhancement technique, and it started giving
-->
me more detail, and then this was sort of an
-->
interesting prompt, which was I kind of asked it to
-->
tell me the subsystems of the electron microscope
-->
and tell me some of their parts, and if you look
-->
at the domain objects column here, it came up
-->
with things like a pumping system and the sample
-->
chamber and the secondary electron detector and the
-->
backscattered electron detector, and all of these
-->
are nouns that are in the problem domain, and it's
-->
kind of subjective which ones you want to add to
-->
the domain model, but the rule is kind of things
-->
that the user of the system would sort of
-->
intuitively understand. So if you're using an
-->
electron microscope, you probably have some idea
-->
that there's an electron detector that looks at
-->
the electrons that are bounced off of the
-->
sample. While I wasn't and I'm not a domain
-->
expert on electron microscopes, I had in a past
-->
lifetime worked on a system called an electron
-->
beam lithography system, which is used for
-->
semiconductor manufacturing, and hardware wise
-->
what's in an electron microscope and what's in
-->
an E beam lithography system are pretty similar
-->
to each other, completely different use cases,
-->
but hardware wise there's still what's called
-->
a sample stage, which is where you put the
-->
sample that you're examining under the
-->
microscope or where you put a silicon wafer
-->
if you're doing VLSI kind of lithography
-->
things. And that sample stage is essentially
-->
a platform that can move in two dimensions,
-->
X and Y. I guess in a microscope it can also
-->
move in Z, but it's you kind of put your
-->
sample on this stage and the stage moves around
-->
back and forth, and then the electron beam
-->
kind of comes down this column and it impinges
-->
on the sample. And so I used a little bit of
-->
my own domain knowledge and a lot of my
-->
experience in building domain models for
-->
hundreds of different projects to kind of
-->
break this down a little further.
-->
So Elena, are you back yet? No. Okay.
-->
Well, I think Elena's going to get behind
-->
a little bit because we need to sort of
-->
keep moving at this point. So what
-->
your job is going to be next is to go
-->
back into Cameo and we're going to basically
-->
add to the diagram we were building
-->
and build it into parts, kind of a
-->
hardware part, which I put on the left,
-->
and a software part that
-->
sits over on the right side of the diagram.
-->
So I'm going to actually put my
-->
slides on my second monitor here so I
-->
don't have to switch back and forth all
-->
the time, my second monitor being
-->
lower resolution than my first monitor.
-->
And, whoops, where did it go?
-->
Nope, that's not it.
-->
Oh, bear with me for a second while I find
-->
where my slides went.
-->
I think it went here.
-->
So what you can do is you can start
-->
Cameo and start expanding
-->
your domain model, and I will
-->
do the same here in a minute.
-->
I've got a question. So, I mean, it doesn't
-->
really look like it lines up one-to-one with what we were creating
-->
before. How does that plan out?
-->
So you can either make a new diagram or you can just
-->
modify the diagram that
-->
you had started. And we'll probably have to regenerate the glossary
-->
at the end of it. But I think there's probably enough
-->
in common with it that you can
-->
just modify the diagram that you've had.
-->
If I can find my DAW desktop again.
-->
I may have to open it up again.
-->
What?