Software Engineering: A Practitioner's Approach

by Roger S. Pressman

For over 20 years, Software A Practitioner's Approach has been the best selling guide to software engineering for students and industry professionals alike. 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.TAKEAWY HERE IS THE AGILE PROCESS METHODS ARE COVERED EARLY IN CH. 42. NEW PART ON WEB APPLICATIONS --5 CHAPTERS

Genres: Computer Science, Programming, Technology, Nonfiction, Software, Reference, Technical

880 pages, Hardcover

First published January 1, 1982

Reviews

[Adam Turoff · Rating 1 out of 5]

A poor textbook for a murky field of study.

Sadly, software engineering is a big grab bag of topics necessarily focuses on how high ceremony, high discipline projects work. Real projects almost never see the kinds of specialization and formalism described in a software engineering class, except for big ticket, high cost, cannot fail, bureaucratic projects. Unfortunately, those projects have very little in common with each other, and even less in common with everyday projects, especially those using any of a number of agile methods.

Yet the text paints everything with a broad brush, giving the impression that every project should have a staff of 20 dotting i's and crossing t's, while simultaneously giving the impression that you can choose any of a, b, c, ..., q, r, s, ... w to structure your project, oh wait, you need to do some of (a, b, c) and some of (d, e, f), oh, wait, those steps are optional too, maybe.

The text reads like an accretion of paragraphs written over several revisions, never edited for readability, consistency, currency, applicability or accuracy, just so long as it has "plenty of examples" and drops enough references to notable names, papers and approaches to appear comprehensive. Without ever vetting that the tools, techniques and examples references are in any way actually relevant or in use.

Hardly a practitioner's approach to software engineering.

[Milad Khajavi · Rating 1 out of 5]

تا فصل ۱۱ این کتاب رو از ترجمهٔ نوید هاشمی‌طبا خوندم و از فصل ۱۲ تا ۲۳ش رو از ترجمهٔ جعفرنژاد قمی.
در مورد ترجمه‌ها اصلاً صحبتی ندارم که واقعاً کم‌کاری شده در این زمینه.
با خوندن این کتاب دید نسبتاً خوبی برای تولید و توسعهٔ سیستم‌های نرم‌افزاری پیدا کردم اما یک سری ایراد به نظرم داشت:
۱- خیلی خیلی مطاب قدیمی است
۲- این کتاب به جای اینکه نتیجهٔ تجربهٔ شخصی نویسدهٔ کتاب باشه، چیزی مثل جمع‌آوری نتیجهٔ تحقیقات یک سری محققه. نویسندهٔ کتاب سعی کرده مجموعه‌ای از نتایج تحقیقات چاپ شده در زمینهٔ مهندسی نرم‌افزار رو در این کتاب بگنجاند.
۳- خیلی از روش‌ها تقریباً قدیمی شده و دیگر کاربردی ندارد
۴- خیلی از روش‌ها اصلاً شناخته شده نیست چه برسد به اینکه قدیمی هم شده است.
۵- مثال‌های کاربردی این کتاب چندان راهگشا نیست، خیلی از مسائل هم که در حد نظری بیان شده. بدون هیچ مثالی.
۶- متن خیلی خسته کننده‌ای داره.
۷- به روش‌های شئ‌گرا کم‌تر پرداخته شده است.
۸- گاهی آنقدر مطلب افزونگی دارد که حوصلهٔ خواننده را سر می‌برد و گاهی آنقدر خلاصه است که خواننده هیچ سر در نمی‌آورد.

[David · Rating 2 out of 5]

This was a pretty comprehensive (if over-wordy) book back when I was in university. It tries to highlight the current best practices of software development methodology. Unfortunately, it probably doesn't highlight the really up-to-date stuff. Even back then it was more focused on structured design rather than object-oriented best practices, such as doing white box testing and data flow diagrams. There are some gems in there, like the discussions on metrics and formal methods, but the writing is somewhat verbose, making it difficult to sift through.

[Alexi Parizeau · Rating 5 out of 5]

It's not often that I find a textbook which I love this much; it's such a wonderfully lucid journey through software engineering. The writing style is contemporary and compelling, and the content is structured in a naturally linear order, so if software engineering is your thing you might find it a real good page-turner from cover to cover.

[Anjar Priandoyo · Rating 3 out of 5]

I read this book, 20 years ago, still relevant until now. I reread the chapter again. It is about software process, modeling, quality and security, and project management. This book is still and always relevant.

[John · Rating 5 out of 5]

This is one of the best books on software engineering!

[Omprakash]

I THINK VERY USEFUL

[Ravi Ugale]

i think this book is very funtastic

[Ghamdan]

it is anice book

[Wojciech · Rating 3 out of 5]

This is a OK book, but I think it's mostly out of date in 2018

[Hamza Mohammad Khan · Rating 4 out of 5]

It is a good book along with Ian Sommerville's book but there is a lot of unnecessary stuff written in it

[Michael Vincent Solomon · Rating 5 out of 5]

Roger Pressman is one of the best software engineering masters!!!

[Anupam Teli · Rating 5 out of 5]

Good book

[MrPancetita · Rating 3 out of 5]

The translation into Spanish translates the acronyms. That makes it very hard to delve on any topic as no one else uses that acronyms. e.g: ACS instead of Software QA

[Juliano Penna · Rating 1 out of 5]

Very bad. It isn't well written, the sentences are full of abstract words that makes reading it unnecessarily hard. I read about 150 pages and gave it away.

[Tom Newman]

NRO Program Management Course / Offsite - 19 June 2000

[Muhammad Ilyas · Rating 4 out of 5]

This is just the wistage of time

[Y͢i͢Z͢u͢X͢ · Rating 5 out of 5]

Excelente libro sobre ingenieria de software es una de las 2 referencias bibliograficas para los examenes de egreso de la Ingenieria en Sistemas Computacionales me sirvio de mucha ayuda para pasar mi examen de titulación.
Ampliamente recomendado

[Julius Holmes · Rating 3 out of 5]

Traducción al castellano muy mala. Preferible su lectura en inglés.

[Kasper Christiansen · Rating 1 out of 5]

What is the point of writing a book only to fill the pages with references to other peoples work? If Mr. Pressman was able to sum up the referenced articles to a satisfying degree, this might have been worth the read, but all he does is briefly describe the concepts and then pointing to other peoples discussions about it. This book ends up failing in my opinion because it touches a lot of subjects, without ever delivering enough substance (by itself).
If you are looking for a book to point you in the direction of subject relevant articles/papers, this might be the book for you, sadly I was expecting to find some substance here.

[Nathaniel Mathews · Rating 2 out of 5]

If you parse this book properly, there's some helpful ideas in it. But the overview it provides would be typical of a book one fourth the length of Pressman's. The bulk of the text is due to buzzwords and repetition rather than depth. Software Engineering is an important topic, but there are better books to learn it from than this one.

[Irfin · Rating 4 out of 5]

I used this book in the first year in my software engineering master degree. Nowadays I still used this book as a reference in my software development.

Any serious software developer who called themselves a software engineer, must read this book.

[Lyle · Rating 2 out of 5]

This was the college textbook for one of my Software Engineering courses. It's pretty thorough, and is a good (if dated) introduction to the topic of Software Engineering, but not exactly a page turner.

[Will · Rating 4 out of 5]

A great book for learning how to organize software engineering from requirements gathering to implementation and maintenance. However, this book is not about algorithms or programming techniques and will focus solely on documentation primarily through UML.

[mohsenmomeni momeni · Rating 4 out of 5]

Good Resource for introduction of software engineering.

[Hadi · Rating 4 out of 5]

Farsi translation is stench .

[Anwar]

السلام عليكم

[Rajjakhar]

its wonderful

[Cherry · Rating 4 out of 5]

Gives a clear and complete picture of Software Projects engineering

[Ayoob Al Essa · Rating 3 out of 5]

تقسيم الكتاب على الأبواب جيد، يعيب الكتاب أن كاتبه يتفلسف بشكل كبير ويستخدم بعض الكلمات في اللغة الإنجليزية الغير شائعة