Software Engineering A PRACTITIONER'S APPROACH www. A textbook description of software might take the following form: Software is (1) instructions. Software Engineering: A Practitioner's Approach, 8th Edition by Roger Pressman and Bruce Maxim () Preview the textbook, purchase or get a. Software Engineering book. Read 35 Roger S. Pressman. · Rating This is probably the worst textbook I've ever been assigned to read. The book does.
- See a Problem?
- Browse Books
- Software Engineering: A Practitioner's Approach
- Top Authors
- Bestselling Series
Goodreads helps you keep track of books you want to read. Want to Read saving….
Want to Read Currently Reading Read. Other editions. Enlarge cover. Error rating book. Refresh and try again. Open Preview See a Problem? Details if other :. Thanks for telling us about the problem. Return to Book Page. Preview — Software Engineering by Roger S. Presents an engineering approach for the analysis, design, and testing of web applications.
See a Problem?
This book provides information on software tools, specific work flow for specific kinds of projects, and information on various topics. It includes resources for both instructors and students such as checklists, categorized web references, and more.
Get A Copy. Hardcoverpages. More Details Original Title. Other Editions Friend Reviews.
To see what your friends thought of this book, please sign up. To ask other readers questions about Software Engineeringplease sign up. Lists with This Book. Community Reviews. Showing Average rating 3. Rating details. More filters. Sort order. View 2 comments. 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 A poor textbook for a murky field of study. 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, 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.
The organization of this textbook is terrible. Reading and incorporating the facts presented in this book is similar to having a conversation with a drunk person trying to give advice.
This is probably the worst textbook I've ever been assigned to read. The book does contain good information, but the presentation is completely dreadful.
Beyond the dubious format, the anecdotal examples presented in the form of a play are worthless.
Software Engineering: A Practitioner's Approach
They seem to only serve as filler in this nearly page long The organization of this textbook is terrible. They seem to only serve as filler in this nearly page long book. One can only assume these mini-plays were added in an attempt to create a market for new editions to be sold.
We can't have students buying too many used textbooks, now can we? I am eagerly anticipating the completion of this course. The textbook has made this one of the worst courses in my academic experience.
May 21, John rated it it was amazing Shelves: must-have-books. This is one of the best books on software engineering! This review has been hidden because it contains spoilers. To view it, click here. Oct 24, Hamza Mohammad Khan rated it really liked it.
It is a good book along with Ian Sommerville's book but there is a lot of unnecessary stuff written in it. Oct 03, Wojciech Langiewicz rated it liked it. This is a OK book, but I think it's mostly out of date in Feb 17, Michael Solomon rated it it was amazing. Roger Pressman is one of the best software engineering masters!!! 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 What is the point of writing a book only to fill the pages with references to other peoples work?
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 This was a pretty comprehensive if over-wordy book back when I was in university.
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. 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. 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.
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. 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.
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.
Best kick start reference for software development I stumbled upon. You don't have to read it all to get what you want. Gives a clear and complete picture of Software Projects engineering. Apr 23, Anwar marked it as to-read. Mar 18, Aditya added it Shelves: g. Nov 18, Major Doug rated it it was ok.
Too much theory; not enough practice. Nov 13, Rajjakhar added it. Dec 28, Khalil rated it really liked it. Feb 22, mohsenmomeni momeni rated it really liked it Recommends it for: software engineering students. Good Resource for introduction of software engineering.
Feb 24, Hadi rated it really liked it Recommends it for: My teacher. Farsi translation is stench. Readers also enjoyed.