Software Engineering: (Update) (8th Edition) (International Computer Science Series) | 
 enlarge | Author: Ian Sommerville
Publisher: Addison Wesley
Category: Book
List Price: $124.20
Buy New: $52.00
You Save: $72.20 (58%)
New (47) Used (27) from $42.98
Rating:  6 reviews
Sales Rank: 213179
Media: Hardcover
Edition: 8
Pages: 864
Number Of Items: 1
Shipping Weight (lbs): 3.5
Dimensions (in): 9.1 x 7.6 x 1.7
ISBN: 0321313798
Dewey Decimal Number: 005.1
EAN: 9780321313799
Publication Date: June 4, 2006
Availability: Usually ships in 1-2 business days
Shipping: Expedited shipping available
Condition: Great opportunity to save on your book. WE SHIP DAILY!!!
| |
| Similar Items:
|
| Editorial Reviews:
Product Description
" Sensible choice and organization of topics, made all the more authoritative by the author's credentials as a senior academic in the area "Prof. David S. Rosenblum, University College London " I find Somerville inviting and readable and with more appropriate content "Julian Padget, University of Bath " Sommerville takes case studies from radically different areas of SE. This avoids excessive stereotyping (hence blinkering), but permits some depth and detail. " Dr C Lester, Portsmouth University Software Engineering 8 presents a broad perspective on software systems engineering, concentrating on widely used techniques for developing large-scale systems. Structured into 6 parts: 1: Introduction; 2: Requirements Engineering; 3: Design; 4: Software Development; 5: Verification and Validation; 6: Management And now with additional new chapters on System Security Engineering, Aspect-oriented Software Development, and Service-oriented systems!Building on the widely acclaimed strengths of the 7th edition, 8 updates readers with the latest developments in the field, whilst maintaining the structure and content of the 7th easily upward compatible for those using the text in a teaching environment.
|
| Customer Reviews: Read 1 more reviews...
 A nice book in software engineering February 2, 2007
M. Lutfi (Santa Rosa, CA USA)
6 out of 6 found this review helpful
I bought this book as a required textbook for my grad course. I've learned a lot from my past misconception and misunderstanding between software science and software engineering just after reading a few chapters from the book.
The book covers wide aspects of engineering a software, both technical aspects and non-technical aspects (social, laws, ethics) although not in deep-breath details.
I highly recommend this book for any students who want to know about software engineering, pracicing software engineers who want to enhance their engineering ana managerial capability in developing a good software or for self-study for anybody who want to jump into software business.
see new chapters on Web Services and Aspect programming December 26, 2006
W Boudville (Terra, Sol 3)
11 out of 14 found this review helpful
It has been 2 years since Sommerville put out the 7th edition of this book. So what has changed? Three new chapters have been added at the end of the 8th edition.
One is entitled "Service-oriented software engineering". All about Web Services, which is a burgeoning field. The 7th edition just had a relatively brief explanation about XML and the sundry services developing atop it. Now the 8th edition goes into those, like the Web Service Description Language, and the Business Process Execution Language. To be sure, the chapter is not an exhaustive explanation of the syntax and usages of these languages. For that, you need to consult books devoted to them (and these do indeed exist). Rather, the chapter furnishes a concise overview that gives you the essence of what they can do. I actually think the chapter should have been simply called "Web Services". The actual title, while accurate, is too indirect.
Another new chapter looks at aspect oriented programming. Again, just an overview. But it does convey accurately what AOP offers. Centred around the key idea of cross cutting concerns. And that conventional object oriented code tends inevitably to have closely related code scattered thru many classes; making maintenance harder. It is by no means clear that AOP will ever become common. But it is one of the most intriguing ideas to arise recently, and Sommerville is correct in explaining it.
In the existing chapters brought over from the 7th edition, I do still disagree with his remarks on Extreme Programming. While XP does have some laudatory features, I take issue with the constant refactoring and the pair programming, as well as having a customer onsite at the developers' place. The latter is simply not realistic in some projects.
While pair programming, and not having programmers responsible for specific parts of the code, totally ignores different levels of expertise. Some programmers are simply better (or more experienced) than others. A real danger is having 2 neophyte programmers unwork complex code made by a senior programmer, that they simply did not understand. If you have done any programming, you will encounter subroutines that are highly intricate and intrinsically hard to understand. Typically, these subroutines are only a small part of the total code. But they might play a crucial part. They should be associated with specific programmers, who are responsible for them.
Another reason against pair programming is when the programmers are not just "pure" programmers. They might have backgrounds in various engineering or scientific fields, where this background is needed for the project. So a programmer/engineer versed in mechanical design, and who has to code accordingly, has different responsibilities from another programmer who has to deal with modelling the electrical circuitry, for example. At the design level, it makes eminent sense to sometimes pair these, when the domains overlap. But at the programming level, each can't usually do the other's work.
Good high-level book April 10, 2007
G. L. Sinsley (State College, PA United States)
2 out of 2 found this review helpful
This is a good high-level book for a first software engineering course. It mentions things like critical systems, object oriented programming, and real -time systems, but at a very high level; so it should not be used for a specialized course. It provides many helpful examples and diagrams. My only complaint is that the chapters are very long, and a lot of things are repeated several times. I think this book could easily be 75% shorter without loosing any important information.
Comprehensive September 16, 2007
Danny Massimini Jr. (SLC, UT USA)
1 out of 1 found this review helpful
This book is a good book to learn from, it can be a little boring at times but in general it is a good study tool that keeps subject matters seperate where they should be
 too bloated March 12, 2008
S. Willis
it feels like this book goes out its way to stretch easily understandable concepts into a huge 900 page book.
|
|
|
