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
-->
All right, 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, and under other
-->
diagrams there's something called a glossary table.
-->
And what we do with this glossary table is we're just going to take all of these
-->
blocks and 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.
-->
I'm sorry, I'm attempting to drag onto the glossary.
-->
Am I missing something?
-->
Yep, just drag them over from the containment tree into the empty space on the diagram.
-->
Oh, just into here.
-->
And then just add the selected elements to the table.
-->
I think it's just, 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.
-->
We 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.
-->
Cool.
-->
Thank you so much.
-->
My goal was to get us through this by lunchtime.
-->
So it is now lunchtime.
-->
Right to the minute, Maria.
-->
And so we'll see you back here at 1.30.
-->
Thank you.
-->
See you soon.
-->
Yep.
-->
I think we're good, Maria.
-->
It ain't broke.
-->
Don't fix it.
-->
That's true.
-->
Okay, so I'll see you in an hour unless there's anything else you would like to discuss right now.
-->
No, I think we are, we're off and running and actually got through the first lab before lunch, which is great.
-->
So, all right, see you in an hour.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
It is a garage. They can go right into that garage. They know where it came from and where it went.
-->
And for some reason they don't want to comment on saying what it is.
-->
Our military notes and our president notes.
-->
And for some reason they want to keep people in suspense.
-->
I can't imagine it's the enemy because it was the enemy that blasted.
-->
Even if they were late, they blasted.
-->
Something strange is going on.
-->
And for some reason they don't want to tell the people in this shit because the people are really...
-->
I mean, it happened to me over at Bitmix.
-->
They're very close to Bitmix.
-->
I think maybe I won't spend a weekend at Bitmix.
-->
I decided to cancel my trip.
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
Hello.
-->
Hello.
-->
Welcome back.
-->
All right.
-->
I'm migrating to a new target data center for my connection to the DAW desktop.
-->
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, but it's been about a minute and a half for it to connect.
-->
That's not much faster.
-->
Okay.
-->
I heard something about the desktop.
-->
Oh, yeah.
-->
A pop-up came up and said that I could get a better connection if I migrated.
-->
And I clicked yes, and that was a minute and a half ago.
-->
I see.
-->
So you get the up of it.
-->
Interesting.
-->
Oh, I'll cancel.
-->
I'm fine.
-->
Oops.
-->
Who's that?
-->
You know, the thing with time, you know, it's tricky.
-->
It's slow in general sometimes.
-->
So I'm not really sure why you have this window pop, where you just get to a faster speed, I guess.
-->
But if everything works earlier, then let's keep it as a...
-->
Yeah.
-->
Thanks.
-->
So Elena and Daniel, are you guys back?
-->
That's a yes from Daniel.
-->
Okay.
-->
Well, while we are waiting, let me once again ask for some feedback.
-->
How's everybody doing?
-->
Are we still on a good pace?
-->
Too fast?
-->
Too slow?
-->
Too deep?
-->
Too shallow?
-->
Where are we at?
-->
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.
-->
Oh boy, I ran out of coffee, so I'm a bit of a pickle over here.
-->
But otherwise, lunch is good.
-->
Yeah.
-->
If we need to pause for people, that's great.
-->
And I've got my moments where I get behind, so yeah, no, I'm fine.
-->
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, you know,
-->
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.
-->
And it's also nice to see what they're struggling with.
-->
And then because other people are having the same problem, so I'm like,
-->
oh, yeah, I do have to explain what this little weird-looking
-->
barcode button up here means.
-->
They don't just know it.
-->
So 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?
-->
I'd like to mention early on, there's a 3,000-page manual that's pretty
-->
incomplete, so don't expect to like immediately understand and know it.
-->
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 things that happens if you actually write narrative 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.
-->
So, yeah, I taught a live in-person class last week, and, you know,
-->
there was one guy in the class who kept thinking he's in expert mode
-->
because it says expert on a screen.
-->
You know, why would anyone ever think that?
-->
I don't know, but, you know, it's like.
-->
It's crazy.
-->
We began around 2001.
-->
I was going to start up a week.
-->
We were using the beta version of the software.
-->
It would crash about every hour.
-->
So, yeah.
-->
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 is strange.
-->
It fell apart.
-->
It was free.
-->
You know, 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.
-->
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.
-->
So, by the way, these domain objects didn't come out of thin air.
-->
They came out of me asking chat CPT.
-->
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 chat GPT.
-->
And by the way, I exported it to.
-->
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 is, I just said, give 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 I was kind of on a zoom call with Tim and 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 to 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 name. He gave it a name of 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.
-->
Nano 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, 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 a 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, 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, 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, you know, that looks at the electrons that are bounced off of the sample.
-->
And I had, 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, you know, 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.
-->
Okay.
-->
And so, Elena, are you back yet?
-->
No.
-->
Okay.
-->
Well, I think Elena is 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?
-->
Oh, bear with me for a second while I find where my slides went.
-->
Oh, 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's that playing 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 had.
-->
If I can find my desktop again, I may have to open it up again.