I don't think the description of this book adequately addresses the question of who is the intended audience. As I see it, computer science is for people interested in the various computer related "systems" (databases, graphics, networking, operating systems, architecture, and so on). Software engineering, on the other hand, looks at the software development cycle, including gathering specifications, testing, quality assurance, human computer interaction, and so on. This book seems geared toward this latter, with chapters addressing such topics as:
* Physiological Measure for Game Evaluation
* Organizational Challenges for User Research in the Videogame
* Heuristic Evaluation of Games
Written by a variety of authors, each chapter offers experience- and research-based advice on improving video games, but the advice seems aimed more at the software engineer or the video game company CEO than at the programmers in the trenches. Indeed, one of the chapters is actually an interview with such a CEO, in which he discusses the importance of usability and design standards.
This could be a good textbook for a software engineering course, or even for the programmer interested in stepping back and looking at the "big picture" of video game usability. My only disappointment was in not realizing in advance the intended audience.