OK, very good.
So that was using all big examples.
Now we're going into pattern recognition.
So this is also a technique that you use when you kind of see it and see the need for it.
So I would go through a very concrete example of a concrete case of pattern recognition that actually
struck me.
It was like 10 years ago and the situation.
But I see this all the time as well.
And after this, we're going to talk about more how you apply general patterns.
But this is actually a pattern that starts to evolve in your own model.
So conceptually, unknown patterns could start to emerge when inspecting the evolving diagram that you
actually doing on the workshop or after when you're documented as well, you can see them and try to
spot them and try to use them to simplify them.
So let's take a concrete example about when doing logistics, conceptual modelling, about the marshalling
yards and what is going on on the March marshalling yard.
So my question here is, can you stop the pattern?
So I was going to show you now a conceptual model or part of a conceptual model for the domain of marshalling
yards.
And you can probably have different terms here as well.
But this is one way of looking at it.
And then I would like you to see if you see the patterns.
So I will first show the picture a couple of seconds.
So I also go through the diagram without actually speaking them out loud.
And then we're going to talk and then we're going to highlight them to see what to do about them.
So here's the diagram.
So to read this, you can maybe start in the upper corner, if you like to say that a chunder team is
responsible for doing, for example, customer orders and a customer order would result in a customer
shunting, which is to actual activity.
And you when you do a customer something, you change a couple of railroad track from a destination
track to a source track.
Right.
The Assunta team is also responsible for doing flat sorting.
And if they don't do that, then they do that based on assorting notice.
And the flat sorting is also moving a couple of railroad cards from the destination to the source track
sorry, from a source track to the destination track, I should say.
And then the shuttle team could also, based on the martialing order, do whump sorting where they will
actually then move a couple of railroads, railroad cars from source and track to a destination track.
So do you see the patterns?
I think you now start to see the patterns.
I hope so.
Let's highlight them.
So here's something that is quite common, isn't it?
So we have three different classes here that are actually tying into the same class of all being a track
in very much the same way.
We have here one type of pattern.
Right.
Here's one type of pattern and here's one type of pattern.
So there is a couple of different things here that are very alike.
How should we do to try what should we do to try to to simplify this?
So step one generalization of shunting.
So then I would probably ask the facilitator, if I spot this, say something like it looks like the
hump sorting, flat sorting and customer standing are very similar.
Do you have a more general term that you use for all of them?
So that's a question I could raise and maybe the experts would then say, yeah, I suppose that that
will be just chanting, OK, so let's use that.
So let's say the tump sorting, flat sorting, customer shunting are all subtypes of subclasses of the
class on the abstract class something.
And then we connect what they have in common from the shunting class instead.
So we remove a lot of associations that were actually common in all those three classes and put them
on the abstract class instead.
So it's something that moves railroad cars from a source to a destination track.
OK, very good.
And then we say that is martialing order, sorting order and customer order, which are performed by
Shunda team.
They perform still the three different types of Shantee.
Very good.
So step two, then we will probably like to do the same thing, but foxhunting order as well.
So then I can ask a question saying how about the martialing orders and sorting notice and customer
order on?
They also just different kinds of shunting orders.
Right.
So then if they then ask a question, answer that question, saying, yeah, we will call that probably
then the shunting order, then that will be a super type and abstract class for the marching order,
sorting notice in customer order.
And then we connected like this and then we move the connection to the chunking team up to the abstract
shunting order concept.
So now we have removed all of the things that were common in all these subtypes or what is now subtype.
So two super classes instead.
So we started off with this.
We had that before and after we got this.
And at least I think the the the result after is much easier to understand because you have less connections
and they are much more clearer and it's much easier to actually modify and extend if we need to have
more subtypes.
We just adding some subtypes.
So this is a very typical example how you could restructure a module during the workshop to actually
gain knowledge as well.
So you gain knowledge about how people are maybe having knowledge about the domain on an even more abstract
level, on the general structures that are underlying the concepts much better.
Now, let's continue with your story.
You said there were two types of stations and so on.
So you do this restructuring, you could either take a break in 10 minutes, you can do it in the model,
or if you have fast enough in your in your modelling tool, you can maybe do it on the fly.
It's depending on your skill.
So here's also what you need to practice the tools you're picking.
Very good.
That was the example or pattern recognition in a specific model.
Now we're going to go into how you can actually use.
General conceptual patterns that you can read about and learn prior to the workshop and then use during
the workshop.
That is a very powerful tool.
I'm going to show you that good either.