I teach a course in software engineering nearly every year, and am always trolling for a new and better textbook. This book does not come close to satisfying my needs. While the breadth of the coverage is adequate, the depth is too shallow. If the course were structured so that the students read the book and took the test, then it would probably be minimally adequate. However, I have them develop and describe a software project using UML and only three pages of this book are devoted to UML diagrams. This is nowhere near enough for explaining what is nearly the standard means of expressing software development.
While I commend the authors for including a chapter on software maintenance, it also covers software support and is only twenty pages long. I really have no desire to teach my students how to accept and manage customer support calls. And quite frankly, they have no desire to learn how to do it. These weaknesses are unfortunate, because I found the book to be the most readable of the software engineering texts that I have examined. Very little code appears in the book, three pages are devoted to function point estimation and the phrase lines of code (LOC) doesn't even appear in the index. I also could not find the word metric anywhere in the index.