<< 1 >>
Rating: 
Summary: Terrible Book
Review: Absolute worst book that I have ever seen. I wish that I could rate this book as 0 stars. Questions at the end of the section are confusing. The chapters are extremely shallow in the coverage. Wiley is a well known publisher. I don't know how this book slipped through the cracks.Figures and Tables: The figures and tables are of poor quality. Many figures are not even refered to in the text. Many of the tables have a squished font. Some tables are sideways. General poor quality: Book looks unprofessional. Many typos. Items don't line up. DO NOT EVEN CONSIDER ADOPTING THIS BOOK FOR A COURSE.
Rating:
Summary: Terrible Book
Review: Absolute worst book that I have ever seen. I wish that I could rate this book as 0 stars. Questions at the end of the section are confusing. The chapters are extremely shallow in the coverage. Wiley is a well known publisher. I don't know how this book slipped through the cracks. Figures and Tables: The figures and tables are of poor quality. Many figures are not even refered to in the text. Many of the tables have a squished font. Some tables are sideways. General poor quality: Book looks unprofessional. Many typos. Items don't line up. DO NOT EVEN CONSIDER ADOPTING THIS BOOK FOR A COURSE.
Rating: 
Summary: Difficult but comprehensive
Review: I have been looking for the most comprehensive book on Software Engineering to be used by both my colleagues in my software company... and my students in Cairo University.
I found this book to be a comprehensive one stressing a quantitative approach compared to other more popular books like Sommervile, Fleeger, etc. The book covers most of the topics with case studies, a lot of Exercises, and reference to software engineering standards.
I am really surprised that this book is not popular and I definitely recommend it to the community so as to be able to build better software.
Rating:
Summary: A Bad Book for Teaching Software Engineering Class
Review: The book was written in a poor organized manner comparing with those written by Pfleeger, Pressman, ... Lack of materials can be adopted by students to solve problems after each chapter. Some exercises are vaguely related to the materials in each chapter. As far as I am concerned, students must understand materials from other books before they can apply their understandings to solve problems in each chapter of this book. IF YOU CONSIDER THIS BOOK AS A TEXTBOOK TO TEACH YOUR SOFTWARE ENGINEERING COURSE, YOU MUST BE AN INEXPERIENCED PROFESSOR OR THOSE WHO ARE LACK OF EXPERIENCE IN SOFTWARE ENGINEERING INDUSTRY. I am not surprised to see why this book has been poorly rated for education. If you want your students to have a fundamental knowledge of software engineering, use different books.
<< 1 >>
| 
