Excercise05 Updates to all subtitle files (#17)

* Update Exercise05-Task1-de.sbv

* Update Exercise05-Task1-en.sbv

* Update Exercise05-Task2a-en.sbv

* Update Exercise05-Task2b-en.sbv

* Update Exercise05-Task3-de.sbv

* Update Exercise05-Task3-en.sbv

* Update Exercise05-Task3-XModeler-en.sbv

Uebungen/Blatt05/Exercise05-Task1-de.sbv

@@ -19,7 +19,7 @@ und mit der nicht ausgemalte Raute eine
 Aggregation und diese beiden sind lesbar
 
 0:00:28.740,0:00:33.660
-von der Seite. Also die Raten sind nicht einfach
+von der Seite. Also die Rauten sind nicht einfach
 Pfeilspitzen, sondern die Rauten sind praktisch
 
 0:00:33.660,0:00:39.000

Uebungen/Blatt05/Exercise05-Task1-en.sbv

@@ -8,14 +8,14 @@ are simplified. So, there are no attributes and
 
 0:00:19.260,0:00:33.660
 no methods. These class diagrams simply consist
-of those boxes and have relationships between
+of boxes and have relationships between
 
 0:00:33.660,0:00:44.400
 them. So, we do not have to look at attributes
 and methods here. We can assume that these
 
 0:00:44.400,0:00:53.820
-classes are (?well-tiered). For instance, this
+classes are well-tiered. For instance, this
 A class here shall be treated as a valid class,
 
 0:00:53.820,0:01:01.440
@@ -31,7 +31,7 @@ between A and B. So, A consists of B's. And
 we have an aggregation where B's consist of A.
 
 0:01:30.000,0:01:40.860
-But this is not problematic because if it were
+But this is not problematic. If it were just
 compositions, then we would have cycled between
 
 0:01:40.860,0:01:50.460
@@ -52,7 +52,7 @@ means B's are also A's. And when this happens,
 
 0:02:27.420,0:02:34.980
 then this means that they also inherit the
-composition where A consists of C's. And
+composition where A's consists of C's. And
 
 0:02:34.980,0:02:41.160
 this would mean that B's consist of C's whereas
@@ -79,16 +79,16 @@ of A and of C at the same time. And this is
 not allowed as the composition rules are that
 
 0:03:43.740,0:03:57.060
-a part can only be a part of (?one
-whole). So, this does not make sense.
+one part can only be a part of one
+whole. So, this does not make sense.
 
 0:03:58.680,0:04:04.620
 So, we could argue that the class diagram
 is valid. But if we say it's valid,
 
 0:04:04.620,0:04:10.560
-then we also have to admit that there is (?no
-instance valid). So, we can also say this class
+then we also have to admit that there is no
+valid instance. So, we can also say this class
 
 0:04:10.560,0:04:21.600
 diagram is invalid. But if you say it's valid,

Uebungen/Blatt05/Exercise05-Task2a-en.sbv

@@ -1,6 +1,6 @@
 0:00:00.480,0:00:06.060
 In this task, we are going to model an online
-ticketing system for theater. For this system,
+ticketing system for a theater. For this system,
 
 0:00:06.060,0:00:11.460
 we are already given a very thorough description
@@ -19,8 +19,8 @@ some additional notes here for the data types
 that we might use in our attributes. We can
 
 0:00:29.280,0:00:35.340
-use some given classes, namely price for
-prices, calendar date for calendar dates,
+use some given classes, namely 'Price' for
+prices, 'CalendarDate' for calendar dates,
 
 0:00:35.340,0:00:39.540
 and time for clock times. We don't need to model
@@ -55,11 +55,11 @@ theater class. And it consists of different rooms.
 We can't really do anything with that yet because
 
 0:01:24.240,0:01:29.340
-we don't have other classes. (?But we'd hold)
-each room, the room is also underlined. So, this
+we don't have other classes. But we're told,
+each room, the room is also underlined so this
 
 0:01:29.340,0:01:36.660
-is going to be a class as well. Has a name, and
+is going to be a class as well, has a name and
 each seat has a number. So, we have room and seat.
 
 0:01:36.660,0:01:42.780
@@ -111,8 +111,8 @@ just start working out the relations
 between the classes here right away.
 
 0:02:48.120,0:02:53.520
-I'm just going to start by reading this
-entry here. Consists kind of implies some
+I'm just going to start by reading a little
+into this here. Consists kind of implies some
 
 0:02:53.520,0:03:00.120
 kind of relation to other Class because a theater
@@ -140,7 +140,7 @@ So, we are going to make that a composition,
 
 0:03:35.640,0:03:44.220
 connecting theater to room. And the composition
-arrow we get from the draw arrow here already
+arrow we get from the drawio here already
 
 0:03:44.220,0:03:49.920
 has some multiplicity here, at least one,
@@ -191,19 +191,19 @@ anything for us yet. But an event is either a film
 or a concert. There is underlines. Once again,
 
 0:05:11.760,0:05:18.120
-tell us that these are classes. So, we have
+that tells us that these are classes. So, we have
 the class event. And we have the classes
 
 0:05:20.520,0:05:30.540
-filmed and concept. Each event has a name.
+'Film' and 'Concert'. Each event has a name.
 So, you have the name attribute in Event.
 
 0:05:31.380,0:05:34.800
 Additionally, we have, for a
 film, the name of the director
 
 0:05:39.180,0:05:47.880
-and the main actor stored. (5 sec.)
+and the main actor stored.
 
 0:05:47.880,0:05:54.160
 For a concert, the name of the conductor and
@@ -241,7 +241,7 @@ joined in the middle here and then just one arrow
 
 0:06:57.960,0:07:04.740
 to the event. But this works as well. We can get
-rid of these extent labels. Draw arrow adds these
+rid of these extent labels. Drawio adds these
 
 0:07:04.740,0:07:09.300
 automatically. But the arrow already means that
@@ -265,7 +265,7 @@ Because the event isn't part of the theater,
 
 0:07:37.260,0:07:42.600
 and the theater isn't part of the event. So, this
-is most likely just the simple association here.
+is most likely just a simple association here.
 
 0:07:45.660,0:07:52.860
 We're not going to use the arrow that draw
@@ -277,7 +277,7 @@ child. This is not really all that helpful.
 
 0:07:59.880,0:08:06.780
 Instead, we are going to add a label that gives us
-some indication of what this association formed,
+some indication of what this association is for,
 
 0:08:06.780,0:08:14.100
 namely conducts. So, the theater conducts an
@@ -329,7 +329,7 @@ and then we can use one of those predefined
 
 0:09:25.440,0:09:34.920
 classes that we were told about in the help
-text, namely the calendar date. (5 sec.)
+text, namely the calendar date.
 
 0:09:34.920,0:09:39.780
 It's important here that we make use of
@@ -344,16 +344,16 @@ to define our own. So, this is really helpful that
 these are given to us. We have the time as well.
 
 0:09:55.800,0:10:00.960
-You need the time class that we are given. And we
-have the price for the seats. Of course, we can
+Using the time class that we are given. And we
+have the price for the seats. Which we can
 
 0:10:00.960,0:10:07.080
-just give us the price. And for that, we're using
-the price class. And that's our three attributes.
+just give as 'price'. And for that, we're using
+the Price class. And that's our three attributes.
 
 0:10:09.780,0:10:13.020
 There's, once again, no indication of
-finding methods here. So, we're going
+any methods here. So, we're going
 
 0:10:13.020,0:10:17.940
 to delete this method placeholder.
@@ -428,7 +428,7 @@ to infinity. So, this can be a relationship of one
 event on however many dates, at least one date.
 
 0:12:21.240,0:12:26.520
-It can really be zero to however many
+It can't really be zero to however many
 here because the text specifically says
 
 0:12:26.520,0:12:32.940
@@ -453,10 +453,10 @@ then add a reading direction, once again.
 
 0:13:02.940,0:13:07.860
 A label with a reading direction
-that says the date a room happens.
+that says,
 
 0:13:09.540,0:13:16.500
-For example, a room is booked for a
+for example, a room is booked for a
 specific date. So, we can say booked
 
 0:13:19.560,0:13:28.500
@@ -469,18 +469,18 @@ date is taking place in a specific room. So,
 
 0:13:40.080,0:14:03.660
 taking place. Or just in. And then reading arrow
-in the other direction. There we go. So, happened
+in the other direction. There we go.
 
 0:14:03.660,0:14:11.220
-in. (? Do like that). So, some kind of date, some
+So, some kind of date, some
 kind of event is happening in that specific room.
 
 0:14:12.360,0:14:18.120
 Speaking of that specific room, the text says a
 room where it happens. So, not multiple rooms. So,
 
 0:14:18.120,0:14:24.480
-this is implicated in the multiplicity of one
+this is implicated the multiplicity of one
 here. You can just leave that as the one here.
 
 0:14:24.480,0:14:31.980
@@ -544,8 +544,8 @@ theater and reserves the selected seats.
 So, we're going to add another method here,
 
 0:16:03.480,0:16:11.160
-which is called "send," which just sends the book
-into the theater and reserves the selected seats.
+which is called "send," which just sends the booking
+to the theater and reserves the selected seats.
 
 0:16:11.160,0:16:17.520
 The booking is being sent away here. So, this
@@ -593,7 +593,7 @@ booking just having a relationship to the date.
 
 0:17:23.340,0:17:33.640
 Namely, being a booking for a specific date
-with reading directed from booking to date. Move
+with reading direction from booking to date. Move
 
 0:17:34.800,0:17:40.980
 a little closer. Let's just leave
@@ -620,11 +620,11 @@ And we're told one or more. So,
 
 0:18:14.640,0:18:19.620
 the multiplicity on the side of the seat
-is going to be one, two, however many.
+is going to be one to however many.
 
 0:18:23.100,0:18:30.240
 And we can remove this multiplicity down here that
-draw arrow added if I can (? get it). There it is.
+drawio added.
 
 0:18:32.400,0:18:39.660
 Because there's no indication that one seat

Uebungen/Blatt05/Exercise05-Task2b-en.sbv

@@ -40,10 +40,10 @@ attributes or methods. So, we're just going to
 
 0:01:09.600,0:01:16.800
 get rid of these placeholders here and just
-leave it like this. Then we have our events
+leave it like this. Then we have our event
 
 0:01:16.800,0:01:23.640
-that are going on. In this case, this is a film.
+that is going on. In this case, this is a film.
 Since this is a generalization going on here, we
 
 0:01:23.640,0:01:30.420
@@ -71,7 +71,7 @@ our class diagram. So, we need those as well.
 
 0:02:16.440,0:02:22.140
 They are given in the text as well. The director
-of that famous Volkert Mort. We have a director.
+of that famous Volkert Mort. So we have 'director'.
 
 0:02:28.080,0:02:30.000
 The main actor is Harry Topper.
@@ -93,7 +93,7 @@ With that, we have the event that's going on
 in our object diagram and its relation to the
 
 0:03:10.800,0:03:17.220
-theater. And we can move on to the dates
+theater. And we can move on to the date
 where this is happening. Or we could move
 
 0:03:17.220,0:03:24.000
@@ -114,11 +114,11 @@ just leave it like that. We don't really
 
 0:03:52.140,0:03:59.640
 know how calendar date types are defined.
-But let's just assume. Writing this down.
+But let's assume it's just writing this down.
 
 0:04:01.020,0:04:06.420
 It's happening next year on a Saturday. Saturday
-doesn't really come into play. But next year, we
+doesn't really come into play here, but next year, we
 
 0:04:06.420,0:04:16.800
 can put this as 2021. Since it's 2020 currently.
@@ -146,7 +146,7 @@ So, we're just going to pull a single line here
 
 0:04:54.900,0:05:09.360
 for which we can copy this. Didn't copy all of it.
-There we go. It's a little fiddly sometimes. So,
+There we go. Drawio is a little fiddly sometimes. So,
 
 0:05:09.360,0:05:16.560
 this is the date of this film. So, this is our
@@ -198,11 +198,11 @@ seat number one for the attributes. And another
 
 0:06:44.400,0:06:54.840
 one, which is going to be seat number two, which
-is going our two booked seats. Both of those are
+is going to be our two booked seats. Both of those are
 
 0:06:54.840,0:07:07.920
 connected to booking via an aggregation,
-as we did in our class diagram. (9 sec.)
+as we did in our class diagram.
 
 0:07:07.920,0:07:16.980
 Some of these pre-made objects aren't that great.
@@ -241,7 +241,7 @@ this room one if we wanted to, just to have one
 object with the actual name. Rooms have names.
 
 0:08:20.400,0:08:26.280
-And the name is given an hour task as well. This
+And the name is given in our task as well. This
 is the "Bluesky" room. So, the name is "Bluesky."
 
 0:08:30.300,0:08:36.720
@@ -261,11 +261,11 @@ very fiddly.
 
 0:09:14.400,0:09:22.860
 I'm not sure what's doing that. But this sort
-of works. There we go. If you're using draw,
+of works. There we go. If you're using drawio,
 
 0:09:22.860,0:09:26.880
 you need to be careful to hit these little
-(?angle points) that show up sometimes. So,
+anchor points that show up sometimes. So,
 
 0:09:26.880,0:09:33.900
 this is our room connected to the seats now and
@@ -280,8 +280,8 @@ here. So, you can pull a normal line to the room.
 And once again, copy this label here, which tells
 
 0:09:50.460,0:09:56.760
-us that this event is happening on this date.
-There's something happening in that room.
+us, that on this date there is something
+happening in that room.
 
 0:09:57.900,0:10:04.320
 And looking at our task description again. See
@@ -293,7 +293,7 @@ going on. We have a room named "Bluesky." We have
 
 0:10:10.920,0:10:15.360
 our two seats. And we have
-our bookings. So, that's our
+our booking. So, that's our
 
 0:10:16.440,0:10:20.400
 object diagram dealt with as