1- very heavy on process management. Not against studying it, but 70% is a lot. Also it isn't a very objective area of knowledge, there's hundreds of ways to skin the pig, which probably explains why it takes so much space.
2- a whole chapter about architecture, which isn't a very well regarded as an independent branch of computer science/systems engineering knowledge.
3- at last, in the technical section, databases shares a section along with fundamentals like processes and operating systems?
All in all it looks like a dictionary/checkbox built by a comittee rather than a consistent perspective on software.
And as a textbook it's got problems as well as mentioned, it has a doubtful taxonomy and too heavy on process engineering.
Tl;dr: I'm getting Orange Eating 101 vibes https://youtu.be/pR6z-gm5_cY?t=38&si=F7knCRNcFET7nki7
Anyways, my 2 cents, won't be reading it.