Rating: ![4 stars](http://www.reviewfocus.com/images/stars-4-0.gif) Summary: A classic Review: A book about software engineering without special focus on OOM. You want to become an software enginner. Then this book must be read.
Rating: ![4 stars](http://www.reviewfocus.com/images/stars-4-0.gif) Summary: Excellent Textbook Review: As one of the previous reviewers said, it has broad coverage. But I think it's not that "concise and clear". Case studies are somehow trifling, and not easy to understand, because of the specific domain involved. Sometimes principles are not clearly identified. That's why I give it four stars. Mr. Sommerville is an English man and this book is not written in American English. Some readers might not get used to it. After all, it's worthy of spending money and time on this book.
Rating: ![5 stars](http://www.reviewfocus.com/images/stars-5-0.gif) Summary: superb overview Review: excellent diagrams. concise and clear summaries. brief chapters. broad coverage. the perfect software engineering 101 textbook
Rating: ![5 stars](http://www.reviewfocus.com/images/stars-5-0.gif) Summary: superb overview Review: excellent diagrams. concise and clear summaries. brief chapters. broad coverage. the perfect software engineering 101 textbook
Rating: ![4 stars](http://www.reviewfocus.com/images/stars-4-0.gif) Summary: Solid Overview Review: For a subject as broad as software engineering, Sommerville does a good job of introducing the topics of the still evolving discipline. The text is a good starting point for digging deeper into issues of interest.I also read the 4th edition of this text. This edition is an improvement.
Rating: ![4 stars](http://www.reviewfocus.com/images/stars-4-0.gif) Summary: My good Software Engineering Text Book Review: I am a Software Engineering student and my lecturer told us to buy this book so that it can be used as our text book. I found it very good and it really helps me understand what Software Engineering is all about. I am doing my Software Engineering project now.. and I found that I am in an advantage stage compared to those without this book. So... listen to a student advise... this book is worth the money you are paying for. I wanted to give 4 and a half stars for this book.. but there isn't any option here that let me do this. Guess I have to give this book a 4 stars.
Rating: ![5 stars](http://www.reviewfocus.com/images/stars-5-0.gif) Summary: It reads well Review: I checked several books on Software Engineering but this one was the only one readable by an ordinary human being. I was in for a nice surprise because it has a support page on the web (see "preface") and you can download an updated chapter with recent stuff and examples in Java. At least someone cares to keep up with new things such as UML. I'd give this book 4.5 stars, but someone else says they gave it 4 instead of 4.5, so I'll give it 5.
Rating: ![4 stars](http://www.reviewfocus.com/images/stars-4-0.gif) Summary: Thorough description of the software development life cycle Review: I read this book as a text book for an Introduction to Software Engineering course. The book starts with the planning and requirements stages of software development and progresses through develop, test, and implementation. Terms, processes, and procedures are described. A thorough introduction for a new engineer, or an overview of current trends and buzzwords for seasoned professionals.
Rating: ![5 stars](http://www.reviewfocus.com/images/stars-5-0.gif) Summary: LOTS TO LEARN FROM THIS BOOK Review: I think one of the previous reviewers who gave 1 star is too picky about wordings and slammed the book based on just that. I have read this book and I know there are lots to learn from it. Just take a look at the table of content -- there are 29 chapters of software engineering stuff to digest.
Rating: ![2 stars](http://www.reviewfocus.com/images/stars-2-0.gif) Summary: Informative but not Practical Review: I used this book for an introductory course on software engineering. Although the book gives an expansive view of the field, there isn't enough detail or in-depth examples to make it anything more than an academic treatise. I don't feel that I could use much of what I've learned in an actual project - I would have to resort to more specific references. Now, the premise of having an entire book on software engineering may be more to blame than the clarity or presentation of the material. But software engineering is a practical field, and a software engineering text that doesn't provide practical information isn't useful. For this reason, I cannot give the book a passing grade.
|