Customer Reviews

Software Engineering: Principles and Practice, 2nd Edition

5 star:		(2)
4 star:		(3)
3 star:		(0)
2 star:		(1)
1 star:		(1)

 

 

Having to teach on a new lab course on Software Engineering, i desperately looked for a book that helps me organize the topics i have to teach. Since i have a programming background , i was not so interested in the implementation part, but wanted to know more on the other aspects of the development : designing,testing,maintaining,assesing quality.This book made me look no further. It is a comprehensive book that covers all these aspects, and the case study that it contains it is not too complicated so it can capture the attention of an average student in a SW undergraduate course. In solving this case study the author does not bind himself to a single solution, but proposes and evaluates different architectures.From an educational point of view it is a good textbook

This is one of the better academic books I've seen in this area. It has the basic stuff you'd expect, but the author also presents very good discussions on writing software specs. The appendix includes some IEEE standards on software documentation. A good book especially for software professionals and technical managers.

The section on software maintenance is excellent and would be a good (and not-too-technical) resource for product managers, marketing managers, project managers, and those involved with the software maintenance process -- something more complex and difficult than we usually think.

Software Engineering Principles and Practice by Hans van Vliet is a good textbook which delves into the WHAT of software development, and takes a user through the normal Software Development Life Cycle (SDLC) from requirements gathering to deployment in a production environment. And like good software, each chapter is loosely coupled allowing the reader to get more information on the topic of interest.

This book however does not go into details on the HOW, and was left me a little unsatisfied on best practices, and how to improve my skills as a software engineer.

This book is great for students as well as professionals involved in Software Engineering. It gives students an overview of what to expect in a software shop, but is more of a reference book for professionals to give a little further insight into the different aspects of the SDLC.

Pros: This book has it all if you're looking for a comprehensive collection of information when it comes to software engineering. Very practical book if you're looking to go into the software engineering world.

Cons: the reading can be very, very dry at times.

It covers in-depth software engineering from software lifecycle to management. I bought Vliet's software engineering - principles and practices -, Braude and Bernstein' software engineering - modern approaches -, and Sommerville's software engineering. All of them have their ins and outs but i think Vliet's covers software engineering in a consistent and straightforward manner. It is a must-have if you want to become a software engineer.

Part of my work involves managing software projects, and leading teams of programmers and software engineers. I recently started my private holy grail search: I NEED to find a book that would advance my subordinates from programmers to leaders; from code-writers to application-makers. For this purpose, during the past year I have read many books - mostly software engineering ones.
As most SW engineers in my teams are university graduates, they already possess some theoretical knowledge in software enginering. What they lack is the know-how of translating theory into practice. Such wisdom is normally obtained after years and years of work (if at all). A good book enabling the engineer to climb faster up the learning curve and shorten this learning period would be invaluable to me.

Most SW engineering books teach theory, not practice. Thus, I approached this book named "Software Engineering: Principles AND PRACTICE " with great expectations. In short - I was very disappointed.
Not that it's a bad book. It is well written, and the theoretical part may serve well as a textbook, probably even aiding students to pass their SW engineering 101 course. However, I found the practical part of the book very lacking: No real tips. No real insights. Nothing really bright here. Definitely not something that would help somebody write better applications, produce high quality products on time, and eventually advance his/her career. NOT WHAT I AM LOOKING FOR.

I never received the item. I don't know if the book was lost in the mail or if the sender never sent the book.