Oh, it should work, right? Yes, that's it. And now we can also record. And now we record

in English such that we have a German and an English recording. German recording last

semester. I can post the link to last semester's recordings on StodOn. And a nice thing is

we have subtitles in German and English. And as far as I understood, we can also subtitle this one

in German and English as well. Now he just leaves the room. All right. Yeah, sorry. I was a bit slow

last time, so we didn't finish the first set of slides. So we'll maybe go through this a little

bit quicker. Of course, I will highlight things that are important. But then again, many of the

concepts that we do in the lecture, they also appear in the exercises. And then, you know,

you should know the things from the lecture, of course. And then the exercise, we go into deeper

details on how to apply things and to proceed with that. All right. So last lecture, we introduced

software engineering. We went through the formal definition and we looked at quite a few things,

why software engineering is important. And it's important if you don't do software engineering,

your projects just run into the wall. They cost more. They fail. So you get a lot of trouble if

you don't engineer your software correctly. And this is not just implementation, but it's also

project planning. It's also requirements engineering. So it's much, much more than just coding and good

coding style guidelines. It's also about how to talk to other team players, other people in your

team, how to synchronize with them and agree on coding standards. We will also see, I also mentioned

that last time, that it's not necessarily that there is just one solution for everyone. So other

teams will need other techniques to collaborate successfully and it involves a lot of experience.

So this is also why we don't teach that in the first semester. It doesn't make sense if you don't

have basics in computer programming and have implemented small projects on your own. It doesn't

make sense to think about software engineering. Software engineering is the part when you scale

up, when you want to run big software projects. And at some point you graduate, you have to either

work in industry, you work in academia, it doesn't matter. You will have to work with large software

frameworks. And if they are not properly designed, it will be a huge hassle. But then

happens most of the time if software is very difficult to maintain, they just put it in the

trash can and just throw it away. Because a software is not just running software on data,

it's also good documentation and we need all of that. So therefore we will start with software

processes now. And the software processes is really starting from scratch. Before you start

writing software, you start with a specification. And the process when we come up with the

specification, we will see it's not just writing down. So sometimes people think, okay, I just

write down, I write the specification and things are good. But actually you're supposed to involve

everybody who will be using the software system when you determine the specifications. Because

otherwise you miss important features, important requirements. So that's a big deal. So it starts

before you write the first line of code. You have to talk to people who will be using the software.

If you don't, then you probably end up in a huge mess. So you have to understand what the software

is currently going to do. Also has to do a bit with digitization. When you're writing a new system

and there's a paper process and they're used to fill forms in paper, you want to understand how

they're currently doing the paper process and do want to understand why they're doing this in exact

same way. And then very often the switching to digital technology is much easier if the new digital

process is somewhat similar to the previous process. So you have to notify your supervisor and so on.

I just encountered a new digital process at some university you might know. And the new digital

process now involves that you do everything online. So you file an application form and then you,

so this was for applying for home office for administrative staff. They have to file an

application form and they can have the home office permission only for maximum of two years and then

they have to file again. So how does it work? Well, they, this is before that it was a paper process

and it has been digitized. And the fun thing is when they digitize the process, they exactly copied

the previous process where you fill a form with all the details and you send it to your supervisor.

The supervisor has to sign it. Then you send it to the administration. They have to check whether

all the grounds for home office are fulfilled and then they grant the application for home office.