Software Engineering: A Practitioner's Approach |
|
|
|
| Pressman, Roger |
| April 2004, McGraw Hill, Hardcover, 880 pages, ISBN 007301933X
|
|
|
|
 |
|
| The sixth edition continues to lead the way in software engineering.
A new Part 4 on Web Engineering presents a complete engineering
approach for the analysis, design, and testing of Web Applications,
increasingly important for today's students. Additionally, the
UML coverage has been enhanced and signficantly increased in
this new edition.
The pedagogy has also been improved in the new edition to
include sidebars. They provide information on relevant softare
tools, specific work flow for specific kinds of projects,
and additional information on various topics. Additionally,
Pressman provides a running case study called "Safe Home"
throughout the book, which provides the application of software
engineering to an industry project.
New additions to the book also include chapters on the Agile
Process Models, Requirements Engineering, and Design Engineering.
The book has been completely updated and contains hundreds
of new references to software tools that address all important
topics in the book.
The ancillary material for the book includes an expansion
of the case study, which illustrates it with UML diagrams.
The On-Line Learning Center includes resources for both instructors
and students such as checklists, 700 categorized web references,
Powerpoints, a test bank, and a software engineering library-containing
over 500 software engineering papers.
Features
The book is geared toward both the practitioner and the student,
giving it added value for sudents even after they graduate.
Five new chapters on Web Engineering (Part 3) present methods
for formulation, planning, analysis, design and testing of Web
applications.
The new modular organization allows instructors to use the book
in a variety of different course formats. Options include a "design
course," a "survey course," "management course,"
and a "web engineering course."
The SafeHome case study has been enhanced and extended to illustrate
important topics and to allow the student to better understand
the inner workings of a project team as software is engineered
and built.
New sidebars are used extensively to present complimentary software
engineering topics, suggest relevant tools, and define workflow
for various technical and management activities.
A robust On-line Learning Center accompanies this book and provides:
PowerPoints, testbank, reference library (over 500) software engineering
papers, study guides, and over 700 web references.
A new chapter on design engineering emphasizes important design
concepts and principles and lays the foundation for the four design
chapter that follow.
The coverage on UML(Unified Modeling Language)has been significantly
enhanced for the sixth edition.
A new chapter on agile development considers Extreme Programming
and other agile methods.
A new chapter on requirements engineering that emphasizes technique
that emphasizes techniques for requirements inception, elicitation,
elaboration, negotiation, specification, validation, and management.
Comprehensive and up-to-date coverage of all important Software
Engineering topics.
Customize this book through Primis Online! This title is part
of the Primis Online Database: www.mhhe.com/primis/online
Object-oriented design has been integrated throughout the text
in this edition.
|
 |
|
1 Software and Software Engineering
Part One The Software Process
2 Process: A Generic View
3 Prescriptive Process Models
4 Agile Development
Part Two Software Engineering Practice
5 Practice: A Generic View
6 System Engineering
7 Requirements Engineering
8 Analysis Modeling
9 Design Engineering
10 Architectural Design
11 Component-Level Design
12 User Interface Design
13 Software Testing Strategies
14 Software Testing Techniques
15 Product Metrics for Software
Part Three Applying Web Engineering
16 Web Engineering
17 Formulation and Planning
18 Analysis Modeling for Web Applications
19 Design Modeling for Web Applications
20 Testing Web Applications
Part Four Managing Software Projects
21 Project Management Concepts
22 Process and Project Metrics
23 Estimation for Software Projects
24 Software Project Scheduling
25 Risk Management
26 Quality Management
27 Change Management
Part Five Advanced Topics in Software Engineering
28 Formal Methods
29 Cleanroom Software Engineering
30 Component-Based Software Engineering
31 Reengineering
32 The Road Ahead |
|
 |
|
Review-Date: 7/15/2010 Rating: 4 Summary: Considered the bible of SE by many.
This book is especially useful to me because of the chapters of software testing which are usually overlooked or hardly mentioned in other books.
Review-Date: 1/6/2010 Rating: 3 Summary: Overpriced but Comprehesive
I have found this book overpriced and wanting in many ways. I used it for self study and at least it is comprehensive. Other reviews point out the weakness in this approach and I agree to a point–– but, well did I mention it is comprehensive. It is far easier to research a given issue in more detail once you are aware of it, than to discover what you do not know via divine inspiration. Given that I am not taking a class, but doing self study, I personaly found it very useful in that respect.
Likewise, as an instructor, which I am not, I would find it useful as a baseline offering to be supplemented with other materials.
The price, on the other hand is not acceptable. McGraw–Hill tiles have increased in cost almost 4 x over the last 10 years or so,and the material is not improved.
Review-Date: 10/19/2009 Rating: 3 Summary: Very good and outstanding service
Very good and outstanding service, but items takes to long to arrive.
Thank you for time and business
V/R
INTULECT
Review-Date: 6/27/2009 Rating: 4 Summary: The Good And The Bad
This book is great for learning about different types of tests and models in the software engineering world. I do find the book too wordy in some parts though. Some of the sentences said are not necessary because they are common sense. Overall though, if you are not looking for a book dedicated to programming and looking for a book about practices in the computer industry then I would recommend this book.
Review-Date: 4/10/2009 Rating: 4 Summary: Alright I guess
First and foremost, I have not read all chapters in this book. But from what I have read, from parts 1,2,4, and 5, I agree that the text covers too much and often says that much of the methods are subjected to the particular circumstances of an individual‘s projects. That is, while there are many ways to do a task, you and your team or company has to settle which one you‘re going to use. And this is understandable, while unpleasant.
The pleasant thing would be if there were a concrete solid step–by step instruction on how to do everything. But this is impossible, because various projects may pursue various paths in developing software projects. For instance, while one project has to be done quickly and information gathering is not as wanted, other project may require more time, being laid back, and have all little requirements and details laid out at the beginning.
I understand that author wanted to cover all aspects, all approaches, and various details, and that led to a text that is not the easiest and not the most pleasant to read. But, understanding the complexity of a task at hand, and the variety of methods and opinions surrounding the software engineering, I think this text was informative.
The little quotes inserted here and then, gave this text personal touch and made it less dry. I liked those. ;)
Review-Date: 2/24/2009 Rating: 1 Summary: CS needs a new go–to SE textbook
If this is THE book for undergrad SE principles, it is only another reason why enrollment in CS programs has dropped.
Problem #1. The book advocates software readability, efficiency, and so forth. Well, why not apply those principles to writing? The text is so dense, you can read whole chapters and maybe get only a few take–home points.
Problem #2. Each chapter presents multiple dozens of new definitions and acronyms. Later chapters fail to repeat or remind you of a prior definition or acronym. It would take some kind of autism to have total recall upon finishing a chapter in this book.
Problem #3. The author quotes so many other works, that it appears nothing is of his own original thought. It reminds me of when I was in junior high and was first learning to write essays. I would put as many quotes as possible in an essay in order to make it look official and to try to get by with little understanding or critical thinking of what I was reading. In a similar manner, this text is little more than a regurgitation of other peoples‘ work. The readers feel like they are reading regurgitation, similar to the way it appears regurgitation tastes to a chick from it‘s mother.
Problem #4. The author presents many things backwards in the text. He mentions concepts that he will define later in the text to prove a current point! This poor technique is quite troubling for a reader who is unfamiliar to the current point, much less familiar with the later concept. This book comes off more as a way for the author to tout that he is up on all of his latest readings in SE, not as an accessible presentation for readers new to the subject.
In conclusion, this book only adds to the pile of terrible CS books. I‘m amazed that these get praised by the authors‘ peers. Well, maybe I shouldn‘t be amazed because it seems like CS authors have a conspiracy to keep the bar incredibly low so they can cash in on high textbook prices with low writing effort. The Head First series should be the beginning of a new standard. Perhaps some of the humor of the Head First series needn‘t be used, but clear, somewhat entertaining, example laden, accessible style should be emulated.
I propose that CS programs take seriously a voting system by students as to the clarity of a text and it‘s effectiveness in teaching the material. Maybe those books that don‘t measure up get flagged across all academia, similar to the way Wanted posters were spread for criminals in the Wild West. Seriously though, at the very least, there should be more critical review of CS literature to bring it up to a higher standard. The books that students find it hard to learn by should simply not be used. The time, potential, and possible future contributions to society by students is too important to waste with this drivel being written by so–called experts.
I also propose that someone take up a hobby of translating these poor texts from techno–babble to readable English. It would be an interesting experiment to see which text, the techno–babble version or the well–written version, would fare better in the marketplace. I bet you that someone could cash in on heroically saving students everywhere from the oppression of these painful texts.
Review-Date: 1/8/2009 Rating: 1 Summary: Pressman is too credulous, scope is too broad, examples need to be worked out in more detail, fit together better.
I used SEPA 6th edition as the textbook for CSE 5324 Software Engineering 1: Analysis, Design, & Testing (a graduate course) at the University of Texas at Arlington during the fall of 2007. I assigned chapters 1 through 14 only.
SEPA describes many software engineering methods, techniques, languages, formats, standards, etc. When I read the discussions of each of these, each discussion sounds more like a press release or an excerpt from an abstract of a paper describing the method, etc. In short, I find Pressman too credulous of the claims made by the originators. Pressman needs to be more critical & insightful in order for me to decide whether a given method is appropriate for a project or not.
Also, SEPA is too broad, the examples need to be worked out in more detail, and the examples need to fit together better, as in a worked–out case study project.
For CSE 5325, I now use "Applying UML and Patterns, 3rd edition" by Craig Larman (plus a smattering of other material to fill in areas required in the course‘s catalog description).
Review-Date: 10/15/2008 Rating: 5 Summary: Pressman‘s book on Software Engineering
This is one of my favorite texts on Computer Science. I learned of it in the late ‘80s and have referred to it many times for ideas. I bought a copy a couple years ago for my library because it is the best all around book on the subject. It has provided useful information that has helped on many projects over the years as a software developer, systems analyst, technical instructor and system administrator. It‘s practical and clear, it doesn‘t bog down in pseudo–intellectual fluff and hype, nor is it focused on one lousy proprietary product that seems to be all that some students learn while getting a CS degree. The work is general and high level, but that‘s what is needed in this field, a "big picture view" of things. Forcing methodology to fit all scenarios just doesn‘t work; one must first understand the overarching issues and needs. What is required to design a system... we know the "why", but what is the structure required to make it happen? This book systematically lays out the foundation for effective system development and covers the SDLC well. It doesn‘t provide low level details, nor should it, that‘s a dynamic environment and subject to change without notice. The complaints about this work perplex me. This book appears in all of my training material as a recommended resource.
Review-Date: 6/22/2008 Rating: 1 Summary: Pressman, you are not helping me
This book will bring you up to speed on all the buzz words for all the methodologies, but thats the extent of the book.
This book covers very little of actually process, how to analyze and existing process, how to setup a new process or improve a process. It actually does a very poor job of explaining what sofrware engineering is all about and leaves you feeling that is about writing documents, not about creating reliable, verifiable software.
Review-Date: 12/12/2007 Rating: 1 Summary: Roger Pressman, thanks for Engineering Confusion!
I used this book in my Grad class and I‘m still confused. I don‘t know what to make of this book. On the one hand, I think the author tries to cover most of the important topics, but on the other, the book falls short in intellectual substance.
Problems at the end of each chapter are very time consuming, and in some cases cannot be answered at all. This makes me wonder if the author can answer any of those tough questions that he wants you to ponder.
If you‘re looking for a good SE textbook, don‘t buy this one. You will regret it!
There is nothing much in this text that‘s closely related to what the author is asking you to consider. His book is based on fluff, and lacks the important stuff; just a bunch of snippets.
You will get an "F".
This is by far the worst textbook I have ever read, and isn‘t worth $128 dollars.
Thanks for nothing Roger, but you deserve at least 1 star!
|
|
