Buy new:
$45.99$45.99
Delivery Wednesday, July 24
Ships from: Amazon Sold by: Nikki’s World
Buy new:
$45.99$45.99
Delivery Wednesday, July 24
Ships from: Amazon
Sold by: Nikki’s World
Save with Used - Good
$7.78$7.78
$19.98 delivery July 30 - August 20
Ships from: glenthebookseller Sold by: glenthebookseller
Save with Used - Good
$7.78$7.78
$19.98 delivery July 30 - August 20
Ships from: glenthebookseller
Sold by: glenthebookseller
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Software Engineering: A Practitioner's Approach Hardcover – January 1, 1996
by
Roger S. Pressman
(Author)
Sorry, there was a problem loading this page. Try again.
{"desktop_buybox_group_1":[{"displayPrice":"$45.99","priceAmount":45.99,"currencySymbol":"$","integerValue":"45","decimalSeparator":".","fractionalValue":"99","symbolPosition":"left","hasSpace":false,"showFractionalPartIfEmpty":true,"offerListingId":"IhhTPP8bNFbWgmdEwsRKBXC6A6vgQBGh8erObwqq15x%2FcEjD2JA4uPA900qz4d88rdDJn7IUMmUASq2eS9tP7Rmtfgmr1bWByVq1No0j8bm2DOnD2tRhP%2Bcr9Y0fWY1Z650xiUpmzpVwLZ36nSX%2FwyB0n6L89tcjrGcyR%2BuvE1UHWSSEL5hJeqyLDZ48MJNT","locale":"en-US","buyingOptionType":"NEW","aapiBuyingOptionIndex":0}, {"displayPrice":"$7.78","priceAmount":7.78,"currencySymbol":"$","integerValue":"7","decimalSeparator":".","fractionalValue":"78","symbolPosition":"left","hasSpace":false,"showFractionalPartIfEmpty":true,"offerListingId":"IhhTPP8bNFbWgmdEwsRKBXC6A6vgQBGh7eEbLY3qtNbXGe86tjOSXfVHw%2BXg0%2BPfIFQAW2xZ6IeWsE9N9%2BgfE2AfjrUs8WQxtAVFVbqF%2FmkhDjlZsTF6DPf2VS38xV03nyCzz1mQ9gLhhcPRejU%2FHdcc1h60wKLBTdsnumTmj5gyF9cUTv6mp5vuZKMSaoGZ","locale":"en-US","buyingOptionType":"USED","aapiBuyingOptionIndex":1}]}
Purchase options and add-ons
Well-suited for both the student and the working professional, Software Engineering A Practitioner's Approach recognizes the dramatic growth in the field of software engineering and emphasizes new and important methods and tools used in the industry.
- Print length852 pages
- LanguageEnglish
- PublisherMcGraw-Hill Companies
- Publication dateJanuary 1, 1996
- ISBN-100070521824
- ISBN-13978-0070521827
Product details
- Publisher : McGraw-Hill Companies; Fourth Edition (January 1, 1996)
- Language : English
- Hardcover : 852 pages
- ISBN-10 : 0070521824
- ISBN-13 : 978-0070521827
- Item Weight : 3.2 pounds
- Customer Reviews:
Customer reviews
3.6 out of 5 stars
3.6 out of 5
8 global ratings
How customer reviews and ratings work
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on Amazon-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
Reviewed in the United States on April 1, 2001
The author achieves a commendable balance between breadth and depth. None of the topics are discussed at a superficial level. In addition, this text is written in a highly readable style. External sources are frequently referenced, quoted, and summarized. There is an emphasis on software metrics in chapter 5 and chapter 18. A section on structured methods is contained in chapters 11-14. A section on object-oriented methods is contained in chapters 19-23. Excellent introduction to advanced topics such as formal methods, reengineering, client/server, and computer-aided software engineering. Breaks CASE tools into 23 categories. Each chapter includes a set of problems and points to ponder.
Reviewed in the United States on August 31, 2002
The fifth edition has been in stores for 2 years now, and you are selling the fourth edition which is from 1996 instead of 2000. You should lower your price, as the new edition sells for 114$ elsewhere.
Reviewed in the United States on March 11, 2000
I'm a PhD candidate in Software Engineering, and I have tried to use this text in several occasions both as a student and as a teaching assistant. I have always been disappointed. My largest problem is that the text attempts to do too much, and ends up doing nothing well. There is no analysis of the strengths and weaknesses of different methods. Why/When should I use OO instead of structured methods?
Furthermore, since the book covers so many topics in a limited number of pages, there simply cannot be enough information in order to apply any of them. If you want to try to analyze, design, build and test even a toy problem, there are inevitably a raft of issues that this book does not address. This book does not provide a student a firm grasp of _any_ part of the software engineering process.
Furthermore, since the book covers so many topics in a limited number of pages, there simply cannot be enough information in order to apply any of them. If you want to try to analyze, design, build and test even a toy problem, there are inevitably a raft of issues that this book does not address. This book does not provide a student a firm grasp of _any_ part of the software engineering process.
Reviewed in the United States on November 2, 1998
An industry standard that no software professional can claim to be well-read without.
I was pleased to see (finally) the addition of two chapters on Formal Methods in Software Engineering. This was an unfortunate omission in the third edition that is now corrected.
The price is a bit overinflated, as with most texts on the subject.
Makes for an excellent companion, when compared and contrasted with other current industry texts.
I was pleased to see (finally) the addition of two chapters on Formal Methods in Software Engineering. This was an unfortunate omission in the third edition that is now corrected.
The price is a bit overinflated, as with most texts on the subject.
Makes for an excellent companion, when compared and contrasted with other current industry texts.
Reviewed in the United States on November 2, 1999
This book provide so many useful topic for software staff, project, manager, designer, programmer, test...
It is very good indeed.
It is very good indeed.
Reviewed in the United States on November 12, 1999
i'm using this book for a graduate software engineering course. i don't feel that i've gotten my money's worth. i expected a book that was clear and concise; i found it tobe neither. i've been very disappointed
Reviewed in the United States on March 8, 1998
This book teachs you how to write hundreds of pages of documentation before writing even a single line of code.
If you work for the government or a bureaucratic large company, you may get a promotion for the documentation. If you work for an effeciency oriented small company, you will get fired.
My prediction is: any company that fully implements the author's method of project management will lose in competition and have to lay off half of its programers within 5 years. This was what happened to IBM 5 years ago and may soon happen to Motorola.
As a consultant, the author knows very well how to make a simple problem very difficult to be understood: unnecessary classifications, unnecessary introduction of not well defined abstract new terminologies and so on.
Just look at a couple of examples:
A control is in fact just a binary (true of false) data. Seperating it from other data doubles the pages. A data transaction differs very little from a data transform, but seperating them doubles the pages again.
A good point is: if you don't know how to communicate to your customer, the author teachs you how:
You may send him a short memo, or a report, or a request, or a documentation, ...
You may have an informal chat with him, or you may have a formal meeting with him, ...
You may send him an e-mail, or you may fax him, or you may have a video-conference with him, or you may simply give him a phone call, ...
(you may leave him a message in case he's not in, this is all I can think of to append to the author's list.)
All these methods are well categorized in the book. Hope all readers can benifit from the instruction.
Xiaolong Wu
Loyola Univ. (Chicago)
If you work for the government or a bureaucratic large company, you may get a promotion for the documentation. If you work for an effeciency oriented small company, you will get fired.
My prediction is: any company that fully implements the author's method of project management will lose in competition and have to lay off half of its programers within 5 years. This was what happened to IBM 5 years ago and may soon happen to Motorola.
As a consultant, the author knows very well how to make a simple problem very difficult to be understood: unnecessary classifications, unnecessary introduction of not well defined abstract new terminologies and so on.
Just look at a couple of examples:
A control is in fact just a binary (true of false) data. Seperating it from other data doubles the pages. A data transaction differs very little from a data transform, but seperating them doubles the pages again.
A good point is: if you don't know how to communicate to your customer, the author teachs you how:
You may send him a short memo, or a report, or a request, or a documentation, ...
You may have an informal chat with him, or you may have a formal meeting with him, ...
You may send him an e-mail, or you may fax him, or you may have a video-conference with him, or you may simply give him a phone call, ...
(you may leave him a message in case he's not in, this is all I can think of to append to the author's list.)
All these methods are well categorized in the book. Hope all readers can benifit from the instruction.
Xiaolong Wu
Loyola Univ. (Chicago)