--- product_id: 77457366 title: "Software Engineering: A Practitioner's Approach" brand: "sem" price: "519 zł" currency: PLN in_stock: true reviews_count: 10 category: "Digital Ebook Purchas" url: https://www.desertcart.pl/products/77457366-software-engineering-a-practitioners-approach store_origin: PL region: Poland --- # Software Engineering: A Practitioner's Approach **Brand:** sem **Price:** 519 zł **Availability:** ✅ In Stock ## Quick Answers - **What is this?** Software Engineering: A Practitioner's Approach by sem - **How much does it cost?** 519 zł with free shipping - **Is it available?** Yes, in stock and ready to ship - **Where can I buy it?** [www.desertcart.pl](https://www.desertcart.pl/products/77457366-software-engineering-a-practitioners-approach) ## Best For - sem enthusiasts ## Why This Product - Trusted sem brand quality - Free international shipping included - Worldwide delivery with tracking - 15-day hassle-free returns ## Description Full description not available ## Images ![Software Engineering: A Practitioner's Approach - Image 1](https://m.media-amazon.com/images/I/51viohiWU9L.jpg) ## Customer Reviews ### ⭐ Pissed off *by M***E on Reviewed in the United States on January 20, 2016* This book is a simple scan of the hard copy book. It's just a bunch of images in a PDF file. I made the mistake of renting this book and there doesn't seem to be a way to return the book. The book is completely useless. Never, never buy a McGraw-Hill etext. You can't read the text on a small screen, like a phone. You can't adjust the text size. It's easily the worst purchase I have made on Amazon. I'm pissed off for paying $90 for this piece of crap. You can get the same quality by pirating the book off the internet. ### ⭐⭐ Not sure I would call this software engineering *by D*** on Reviewed in the United States on January 13, 2019* This book is more about project management ### ⭐⭐ Terrible *by R***A on Reviewed in the United States on September 10, 2016* This is a terrible book which makes the implicit claim that software engineering is a much more organized discipline than it actually is, and most likely than it ever can be. I originally gave it one star, but bumped it to two, simply because I'm not sure there is a better book available. Yet, this doesn't make the problem go away.Software engineering, to put it in computer science terms, is carried out in the world of natural language rather than formal language. There are limits to the precision of the meaning of words, and limits to the precision with which formal processes can define human interactions. This would not be a problem if the book accepted these limits, but it attempts to push well beyond them. Pretending to say more than we can say about something results in saying less than we could have said if we hadn't pretended. The book follows the approach of defining words in terms of other words which are themselves badly defined, or promised to be defined later (a promise which is rarely kept), or are self-referential (architecture is architectural). And then, maybe, another model will be introduced which defines the same words differently (demonstrating the words don't really have a particular meaning) or uses different words for the same things, so that terms don't even have consistent meaning across a chapter. Then, these terms are used to discuss processes as if they've been rigorously defined, when they really haven't been. This leaves us pretending to have an engineering discussion with the precision of equations when we are having at best a social discussion with much less precision than that. If you enjoy reading well-built arguments you will constantly find jarring transitions in this book, along the lines of "it follows that," when quite simply, it does NOT follow.And then this is made worse by the fact that this is a modern textbook, with a modern test bank, in which it's assumed that the *correct* answer depends on the exact keywords the author used on page 391, despite the fact that even the author would certainly admit that this is just one way of looking at the thing.As I already said, there might not be a better effort available, but that doesn't mean this book isn't bad. In fact, it's bad enough that taking the class associated with this book made me want to quit studying computer science or even leave college. I won't do that, because the cost of doing so is too great in terms of what I need to accomplish for other reasons, but I view reading this book almost entirely as a cost to be borne in the service of a greater good. Someone, for Gods's sake, please write a better one. --- ## Why Shop on Desertcart? - 🛒 **Trusted by 1.3+ Million Shoppers** — Serving international shoppers since 2016 - 🌍 **Shop Globally** — Access 737+ million products across 21 categories - 💰 **No Hidden Fees** — All customs, duties, and taxes included in the price - 🔄 **15-Day Free Returns** — Hassle-free returns (30 days for PRO members) - 🔒 **Secure Payments** — Trusted payment options with buyer protection - ⭐ **TrustPilot Rated 4.5/5** — Based on 8,000+ happy customer reviews **Shop now:** [https://www.desertcart.pl/products/77457366-software-engineering-a-practitioners-approach](https://www.desertcart.pl/products/77457366-software-engineering-a-practitioners-approach) --- *Product available on Desertcart Poland* *Store origin: PL* *Last updated: 2026-05-12*