WEBVTT 00:10.250 --> 00:10.760 OK, good. 00:10.820 --> 00:15.200 So now we're really off running, so let's be a little bit more formal now, we talked about generically 00:15.200 --> 00:21.170 while AMOL is about on a kind of high level and why we model and also what a domain models, but a little 00:21.170 --> 00:25.130 bit more formally than what is a model and how can you describe a model? 00:25.160 --> 00:28.790 I'm going to use the kind of definition that is used in UML. 00:28.790 --> 00:32.000 And as I said, we're going to use UML for the rest of this course. 00:32.270 --> 00:36.190 And the next lecture I'm going to start talking about or do you Amalia's. 00:36.590 --> 00:41.180 But before we do that, let's talk about how you will look upon the concept of the model. 00:43.110 --> 00:49.890 So according to your email, there are three categories of elements in a model, and the three categories 00:49.890 --> 00:51.870 are classifiers. 00:53.980 --> 01:03.250 Events and behaviors, so those are the top level three categories of all the things that are included 01:03.250 --> 01:06.640 in the model, and then there could be loads of different subtypes of those. 01:08.380 --> 01:15.890 So each of those major category models, individuals in an incarnation of the system being modeled. 01:16.150 --> 01:22.180 So now we're starting to be a little bit tricky maybe here by what is meant by that is saying that, 01:22.690 --> 01:29.200 for example, the concept of a car is modeling an individual in the system being model. 01:34.650 --> 01:39.630 And in this case, the system being model could be a business, for example, so it doesn't have to 01:39.630 --> 01:40.980 be an I.T. system. 01:41.190 --> 01:42.440 We talked about that already. 01:43.110 --> 01:52.650 So a car could model individual cars in a vendor, for example, business selling cars. 01:53.460 --> 01:53.810 Right. 01:56.070 --> 02:02.730 A sales event models individuals of typical sales going on in that business. 02:03.150 --> 02:10.780 And the sales process is describing individual executions of processes in that business. 02:11.550 --> 02:11.970 Right. 02:12.750 --> 02:21.720 So the model includes so sorry, the model, the models, individuals in an incarnation of the system 02:21.720 --> 02:25.010 being models and incarnation is one instance of a system. 02:25.020 --> 02:30.100 So and that is also quite important to think about that the system is actually something you instantiate. 02:30.570 --> 02:33.620 So think about, for example, McDonald's or something. 02:33.900 --> 02:37.320 So there are thousands of McDonald's restaurants. 02:37.560 --> 02:40.980 Each is an instance of a McDonald's restaurant. 02:40.980 --> 02:46.170 But you must be able to describe the system of a McDonald's restaurant separately and then you have 02:46.170 --> 02:49.350 incarnations of that in all the restaurants. 02:51.060 --> 03:00.720 So classifiers first, then a classifier describes a set of objects and an object is an individual thing 03:00.720 --> 03:03.330 with the state and relationships to other objects. 03:03.360 --> 03:09.210 So you see directly here that this ties back directly into what we talked about in the philosophical 03:09.210 --> 03:09.840 foundation. 03:10.020 --> 03:14.640 And that's why I think that it was important to go through that before we do this, because when you 03:14.640 --> 03:22.320 see directly the kind of links that go out from this domain of kind of system development and business 03:22.320 --> 03:27.510 development into the philosophical foundation, and here's kind of cross-functional science going on. 03:28.320 --> 03:36.450 So a car is a classifier and it describes a set of objects, for example, two cars. 03:37.720 --> 03:44.260 OK, events, an event describes a set of possible occurrences. 03:45.790 --> 03:53.260 So in the same way that a classifier describe a set of objects, events describe a set of possible occurrences, 03:53.470 --> 03:58.640 an occurrence is something that happens that has some consequence within the system. 03:58.840 --> 04:05.710 So that's an immediate kind of thing that happens, that stimulates the system in some way or affects 04:05.710 --> 04:06.770 the system in some way. 04:07.300 --> 04:10.330 So then there are a set of occurrences. 04:10.570 --> 04:15.130 So, for example, maybe those are two types of accident occurrences. 04:15.580 --> 04:20.680 I don't know, maybe maybe the the second one is might might not be an accident here, but yeah. 04:20.710 --> 04:28.330 See, my point and we can have an accident event that describes those two accident occurrences. 04:30.070 --> 04:31.570 And lastly, we have behavior. 04:31.960 --> 04:37.040 So exactly in the same way here, behavior describes a set of possible executions. 04:38.410 --> 04:40.720 So an execution is performed. 04:41.290 --> 04:41.650 Sorry. 04:41.770 --> 04:47.080 So an execution is the performance of an algorithm according to a set of rules. 04:48.600 --> 04:51.730 So an example, again, this is one execution. 04:51.840 --> 04:58.260 First, you do a they you do be another execution would be first you do a but then you do see. 04:59.170 --> 04:59.540 Right. 04:59.940 --> 05:04.310 So those are two ways of executing, for example, a process. 05:04.860 --> 05:10.800 So those are two set of possible execution, although they form the set of possible executions, those 05:10.800 --> 05:11.430 two together. 05:11.850 --> 05:18.660 And the behavior, for example, a business process is describing both the possible executions here. 05:18.990 --> 05:24.450 So the behavior will be described as A, then B or C, right. 05:24.840 --> 05:29.400 But an execution can never do or it does either either B or C. 05:29.640 --> 05:33.210 So the two possible executions here is a plan B and an aide and C. 05:35.510 --> 05:40.760 OK, so you see that they are very alike, here are the classifiers, the events and the behaviors. 05:42.440 --> 05:48.440 So moles and this might be very obvious, but it might need to be stated because sometimes you actually 05:48.440 --> 05:49.250 do this mistake. 05:49.280 --> 05:55.760 And quite often I would say some models do not contain objects, occurrences or executions because those 05:55.760 --> 05:58.530 things are the subject of the models, not their content. 05:58.760 --> 06:03.620 So I started off this whole section describing that is very important, that you differentiate between 06:03.620 --> 06:10.340 the subject being model and the model and hence the model never actually contain objects, occurrences 06:10.340 --> 06:11.210 or executions. 06:11.240 --> 06:12.590 They are part of the subject. 06:14.090 --> 06:16.310 So you have subjects out there. 06:17.150 --> 06:20.380 You have models including the classifier of events and behaviors. 06:20.930 --> 06:23.840 However, and here's where it usually goes wrong. 06:25.070 --> 06:29.250 A model can actually model aspects of individual objects, events or behavior. 06:30.320 --> 06:37.130 So, for example, we can have this specific occurrence of an accident that is going out in the summit 06:37.130 --> 06:37.550 area. 06:38.210 --> 06:44.450 And we can model that specific occurrence, not just the event, but actually the occurrence. 06:44.450 --> 06:50.570 We could model some aspects of it and some aspects could hear, for example, B, that we say that the 06:50.570 --> 06:57.340 accident type is a banana slip and the time of the accident was the 11th of March 2011. 06:57.650 --> 07:00.350 That is then called an occurrence specification. 07:00.350 --> 07:05.480 So that specifies a specific occurrence out in the real world. 07:06.080 --> 07:09.070 And then we can also then have the actual event. 07:09.980 --> 07:11.240 So we have an event. 07:11.240 --> 07:12.950 We could have an occurrence specifications. 07:12.950 --> 07:16.370 They are part of the model and then we have the actual occurrence out there. 07:17.000 --> 07:22.730 But the occurrence will be complete, whereas the model will always be incomplete because it's only 07:22.730 --> 07:25.490 showing aspects of the subject matter. 07:25.970 --> 07:31.720 So, for example, the model will never feel pain when you fall somewhere after your slip, right? 07:32.240 --> 07:36.650 So the pain is only precedent in the subject area and model, of course. 07:37.170 --> 07:43.910 OK, Mary may be too obvious, but as I said, I think it's very important here to be crystal clear 07:43.910 --> 07:44.480 about this. 07:46.750 --> 07:53.590 So value specifications or current specifications and execution specifications, model individual objects 07:53.590 --> 08:00.430 of Currentzis and execution within a particular context, so we can actually exemplify aspects of the 08:00.430 --> 08:07.300 real world, objects of the real world, occurrences like this example and of the real world executions. 08:07.460 --> 08:10.010 And they they are part of the model. 08:11.620 --> 08:13.640 So next is a diagram, the model? 08:14.620 --> 08:16.030 No, it isn't, actually. 08:16.570 --> 08:21.250 But many people are actually almost using them as synonyms, but they aren't actually. 08:21.250 --> 08:22.240 And I will show you why. 08:22.540 --> 08:25.510 And I myself actually do use them as Cinnamon's sometimes. 08:25.510 --> 08:27.580 So maybe you have to to live with that. 08:30.220 --> 08:31.670 So diagramed model distinction. 08:32.110 --> 08:37.720 So the model is the think about it just like the database or the store of the complete offer, recursively 08:37.720 --> 08:39.580 composed set of elements. 08:39.760 --> 08:46.360 So elements are, for example, an event or a classifier behavior that describes the system. 08:46.360 --> 08:50.800 So it's the complete set of all the things that we need are in our model. 08:50.830 --> 08:51.670 That's the model. 08:51.850 --> 08:52.960 So think about it here. 08:53.290 --> 08:59.590 This is not a diagram, but it's kind of a conceptual view about the conceptual model, including some 08:59.590 --> 09:00.100 elements. 09:00.130 --> 09:05.660 Write a specific diagram is showing an aspect of that model. 09:05.830 --> 09:10.840 So the first diagram here up to the left might be including three of the elements. 09:10.960 --> 09:17.050 A second diagram might be three, including the same element, one of the same elements from the first 09:17.050 --> 09:22.180 diagram and then two other elements and the jetton on the third diagram and actually also include that 09:22.180 --> 09:23.950 first element and then two other elements. 09:23.960 --> 09:33.520 So you can actually then use diagrams to specify specific aspects that you would like to maybe highlight 09:33.520 --> 09:34.390 for some reason. 09:34.720 --> 09:37.330 So those are maps or diagrams. 09:37.630 --> 09:42.700 But the good thing about a model is that you have this store, so you don't actually have to rewrite 09:42.700 --> 09:48.580 all the diagrams all the time because it's stored in the complete model and then you can just create 09:48.580 --> 09:50.620 and compose diagrams out of that model. 09:52.570 --> 09:58.810 So bear in mind, as I said, that we also use that we often use the term model as a shorthand for diagram 09:58.810 --> 10:04.060 maps, subset of model or the other way around that we use trying and we we mean model. 10:05.950 --> 10:09.040 And just so you have that in mind, because it happens a lot. 10:09.250 --> 10:13.780 So people are talking about conceptual maps, for example, and then we might say conceptual model, 10:13.780 --> 10:18.610 and sometimes it's a conceptual diagram, but maybe I'm meeting the same thing in all three terms here. 10:20.380 --> 10:26.230 So, for example, I might have a model, including a number of elements. 10:26.230 --> 10:29.800 And actually the diagrams as such are part of the model as well. 10:30.870 --> 10:37.590 So I might have one diagram showing one aspect of some of the elements here, some of the the classifiers 10:37.590 --> 10:43.110 or concept party agreement, all agreement and product, and might have a completely different diagram 10:43.110 --> 10:44.790 showing a completely different aspect. 10:44.790 --> 10:45.510 In this case. 10:45.510 --> 10:48.720 It's the packages and I'm talking about packages later on. 10:48.870 --> 10:50.580 They are kind of subdomains within this. 10:50.580 --> 10:53.340 I mean, the subdomain of an agreement, product and party. 10:54.930 --> 10:58.140 So those two diagrams are describing different things, but they're part of the same model. 10:59.110 --> 10:59.960 OK, makes sense. 11:00.130 --> 11:04.240 I wasn't very good, so I missed the third lecture.