3 ms·
When I was doing my Ph. D., I also ended up teaching some software engineering related courses. One thing that struck me and that I've since fixed by becoming a
by jillesvangurp 7y ago
When I was doing my Ph. D., I also ended up teaching some software engineering related courses. One thing that struck me and that I've since fixed by becoming a software engineer was the notion that here I was teaching Software Engineering without any experience whatsoever actually engineering any software professionally. This is the big problem in academic education on this topic: the teachers typically have little or no relevant experience actually engineering software because they have been in university all their life and as such lack experience working for extended periods of time with an actual team on some actual non trivial software. Lets just say that I learned a lot about this stuff after I left the academic world.
A good practical introduction to software engineering should cover a lot of ground and most of it is going to be non technical. Learning how to program is mostly out of scope for a software engineering introduction. Assume the students have already learned some programming language and have some experience building small programs and maybe have already had some algorithm courses, etc. It doesn't really matter what language or tools they use. For the purpose of an introduction, pick something simple where the focus is mostly not going to be fighting with the tools.
The key thing to learn as a software engineer is working with multiple people and the project dynamics that are associated with that. So:
- project management and different roles in software projects, different ways of structuring teams, etc.
- overview of different process methodologies common in the industry and where they came from: scrum, kanban, watefall (don't do this), etc.
- different types of testing and their importance for continuous integration and deployment
- different strategies for estimating cost, complexity, duration, etc. and their flaws and pitfalls.