After working 33 years as a mechanical engineer with a masters degree doing system design and feedback control including algorithm and embedded software, I find this book is an excellent reference. The selection of words to describe the critical perspective in systems engineering practice is similar to my own. I had been tasked after 10 years as a level V systems engineer to write a chapter on System Design Analysis for a large defense contractor as a new addition to their decades old Systems Engineering Process Manual. This book does a better job in partitioning the system life cycle to enumerate all critical stumbling blocks which cost many engineering departments significant losses. This is an excellent reference. I would not find the material comprehensible if I did not already have a significant career involvement in developing complex systems for DoD. This is a graduate level topic. The author makes clear that systems engineering practice is not a software task, and that the new systems engineer delivering complex systems should come from a traditional engineering discipline with a masters degree. I have that perspective and did not start as a systems engineer until I had 20 years employed as both a mechanical design engineer (12 yrs.) and software analyst (8 yrs.).