Software Engineering (9th Edition)

Bought this for one of my software engineering classes, and it turned out to be a great resource. The material is well organized and explains software engineering concepts in a way that’s easy to understand, even if you’re new to the subject. The examples helped reinforce what I was learning in class, and I found myself referring back to the book while working on assignments and projects. If you’re taking a software engineering course or just want a solid introduction to the subject, I’d definitely recommend it.

Wow - this book deserves more stars than it has! This is an excellent overview of the major topics in Software Engineering as they exist at the end of 2011. Most topics are covered at a level of detail that major ideas are introduced and explained in a way that provides both understanding to students and actionable information to industry developers. If you want more information on a topic, at the end of each chapter is a Further Reading section that points to some of the best resources in Software Engineering. Showing this books value, this book is referenced numerous times in the IEEE's Software Engineering Body of Knowledge. I believe it's referenced more than any other source.I have both the 8th and 9th editions of this book. The 9th contains well-thought out updates, and I'd encourage those considering editions to use the latest edition.

I was required to read this for class. I am working on a degree in software engineering, but I have been writing software professionally for 25 years. I found his approach well balanced. After working in the industry for a while, I have learned that there are so many ways to do things and most of them are valuable or applicable in different situations. It is always frustrating to hear an author tell you how one approach, technique, or platform is the right one. In my mind, they are amateurs and I usually will weigh their opinions accordingly. Somerville has a fairly balanced and pragmatic approach to the material. I might have spent more time on certain sections and less on others, but in general I thought this was a good survey on a very complex and large topic. I'm glad my professor chose this book.

Exactly what I needed for class and no need to wait to get it from the school. I was very happy to see that this book was in great condition even though it was a fraction of the cost the college was going to charge me. The means within this book are well illustrated and offer an informed perspective. This book is a must if you plan on beginning a software or developer field.

This book was used for a graduate class in conjunction with other material. It provides a good base of information, though can be challenging to understand for cases where a personal background in the concentrated subject is completely lacking. I found no issues with the redundant material as others have pointed out, though some explanations are a bit lengthy, almost to a rant.

Son's college textbook. It was exactly what he needed for class. It did the job and arrived quickly. Wouldn't have purchased it if he didn't need it for class though

I had the displeasure of using this book for a graduate level course on Software Engineering. We did not use the web site or the online learning tools associated with the book. The professor did use the author's supplied slides.Pros:* Very nice UML diagrams.* Might get recycled into toilet paper.Cons:* Very repetitive. I lost track of how many times a legacy system was defined. This made reading this book extremely boring.* Despite the 2011 copyright date, the material is dated. Computers are still single core, smart phones aren't on the scene, and Sun still owns Java (cue Oracle lawyers).* The back of the book claims it has been updated with new material on open source development. That new material consists of a few paragraphs on the legal issues of incorporating open source into a traditional project. There is nothing on developing software for open source.* The power point slides that accompany the book have problems with the graphics starting about chapter 5. The image quality of the embedded diagrams takes a nose dive and the images are barely readable.* The topics covered seemed very shallow. I'm not sure you'll get much more out of this book then you would reading through wikipedia articles.* The author has a habit of using acronyms without defining them. COTS (Commercial Off The Shelf) was used for several chapters before it was spelled out.* Electronic version (Kindle) has random spaces removed (as noted by other reviewers)* The project schedule charts presented are Gantt charts. It seems the author has never heard of Gantt and just refers to them as bar charts.* Some diagrams are mislabeled.* There was at least one sample XML file that was used for a few problems. The XML was broken making it that much harder to figure out the problems.If you are a professor looking for a book on this topic, please spare your students and find another book.If you want almost the whole book for free, download the slides. Chapter 4 alone is 82 slides (29 pages in the book).The only thing I'd like to get out of this book (besides my money back) is how the diagrams were created. I haven't found anything that comes close to the ones in the book.

It’s in a good condition just as described.

Although the book is a used book, the overall condition is excellent, definitely worth the money!

Il libro dal punto di vista didattico è molto buono è scritto in modo chiaro e semplice, come libro per iniziare questa materia è molto buono

I like this book, it is one of the best readings in software engineering.

Book bought for uni class. Product came within shipping times with no issue.

One of the best software engineering books out there.Used for studies and still being used in the real world. Highly recommend.