Pretty archaic. It stops just after version control, code builds and testing. Nothing on devops - deployments, kebernetes, containers, monitoring, release management, environments (prod, non-prod) etc. All this should be part of "development tooling".
It's a "teach people how to teach themselves to fish" class
this is meant for freshman/sophomore cs students i think its a reasonable start
> All this should be part of "development tooling".
that's not really development, that's operations.
It seems to be an introduction, so just covering the basics is ok. We're still very close to the IT stone age and the IT industry is still quite archaic, so teaching archaic basics isn't that bad. In a lot of areas it's still best to just write your own tools from scratch...