- Hardcover: 792 pages
- Publisher: Pearson; 9 edition (March 13, 2010)
- Language: English
- ISBN-10: 0137035152
- ISBN-13: 978-0137035151
- Product Dimensions: 7.4 x 1.2 x 9.1 inches
- Shipping Weight: 2.6 pounds
- Average Customer Review: 3.5 out of 5 stars See all reviews (50 customer reviews)
- Amazon Best Sellers Rank: #337,767 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Software Engineering (9th Edition) 9th Edition
Use the Amazon App to scan ISBNs and compare prices.
Customers Who Bought This Item Also Bought
From the Back Cover
Intended for a sophomore/junior level course in software engineering.
The ninth edition of "Software Engineering" presents a broad perspective of software engineering, focusing on the processes and techniques fundamental to the creation of reliable, software systems. Increased coverage of agile methods and software reuse, along with coverage of 'traditional' plan-driven software engineering, gives readers the most up-to-date view of the field currently available. Practical case studies, a full set of easy-to-access supplements, and extensive web resources make teaching the course easier than ever.
The book is now structured into four parts:
1: Introduction to Software Engineering
2: Dependability and Security
3: Advanced Software Engineering
4: Software Engineering Management
About the Author
Ian Sommerville is a full Professor of Software Engineering at the University of St. Andrews in Scotland, where he teaches courses in advanced software engineering and critical systems engineering. His research interest lies in complex, dependable systems.
Ian Somerville is the recipient of the 2011 ACM SIGSOFT Influential Educator Award. This honor is in recognition of the tremendous and positive influence that his Software Engineering textbook and companion educational aids have had on undergraduate software-engineering education, as well as his textbooks on Requirements Engineering, and achievements in establishing the SICSA Graduate Academy.
Top Customer Reviews
* Very nice UML diagrams.
* Might get recycled into toilet paper.
* 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.
1. Repetition. Yes - there is repetition and this is not accidental. The book is not designed to be read cover to cover and it is not, in my view, good for the reader to expect them to simply refer them to somewhere else in the book when a concept is introduced.
2. Dullness - some aspects of software engineering are dull. I have always hated testing and I can think of no way of making software testing and quality management interesting. But they are still essential for professionals - this isn't supposed to be about entertainment. All professions have dull aspects to them and it would be a disservice to readers to pretend that this isn't the case.
I think I have to give a rating for this so, for fairness, I've rated it the average shown.
However, I believe the author is NOT trying to provide the readers every detail about everything he is talking about. If I would teach a SWE course, the book would take me 2-4 semesters to cover. Just think about it, I can write a series of books talking about testing alone, about architecture alone, about XP in Agile alone, about......... This is not the book that give you the whole detail. However, why do so many professors choose this book as their textbooks(the 9th edition at least shows something)? Because it DOES provide a great overview about the key problems in SWE and most of the popular solutions to those problems. Also, it is the professor's discussion in the lectures and the labs that are more important to students who really wanna learn more about SWE. You MUST do projects, coding, putting those theories to practice to know that SWE really is. Even if the author put thousands of questions on the back of the book won't help you learn SWE.
Get the big picture from the book, get the detail from the professors and other good resources. Learn what SWE really is through projects.
To those who wanna learn SWE by yourself:
ok......I have to say that is really tough. If you are in a company, you may don't have a lot of time, otherwise you may don't have project opportunity. As this book contains a lot of information while not that much details, it will drive you crazy sometime. So, this book only worth 2.5 stars for you :< the 2.5 stars are for you to grasp the big picture.
Most Recent Customer Reviews
it is like the root of the tree..
Not every thing in "Software Engineering" will tell you , but you...Read more
Bought used,...Read more