Customer Reviews

Classical and Object-Oriented Software Engineering with UML and Java

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

 

 

If you are looking for an introductory book on Software Engineering, this is probably the best choice. It is comprehensive in content, accurate in explanation, and up-to-date in material (e.g. UML). Plus, it is entertaining to read, you won't get bored with it.

I have been in the SE Industry for several years and have dealt with a wide variety of businesses and corporations. This book not only gives computer professionals a very solid foundation on the proper methodologies and processes but it is also an excellent tool for helping lay-persons understand how important these processes and methodologies are to the software life cycle. This book has become my most valued resource in my professional work.

The original version of the book was written in 1990 and despite the updated title and the notation 4th edition, there is much in this book that hasn't been updated. The UML aspect of the book is very weak and Java is given only a cursory treatment.

The (obviously) older material is well presented and well referenced as chapter end notes but newer topics such as Extreme Programming (Beck), Refactoring (Fowler), etc. are absent from discussion completely.

If you're looking for a good UML book try "UML Distilled" (Fowler) which provides a succint overview of the topic in considerably fewer pages. If you're looking for a book on Software Engineering there are several offerings which provide a solid, more current overview. This book attempts to do both and ends up doing neither.

This book is one of the worst I have ever encountered in my seven-year CompE & CS academic history or in my six-year "real world" experience.

Most importantly, its first copyright date is 1990, and I don't think it had modern ideas then. Yet, in the fast-moving world of computers, he has neglected much networking, any mention of open source software, any mention of bazaar-style development, any depth of databases, thoughts of providing services, recognition of abstraction layers beyond machine code--source code--operating-system, any development of design patterns, and much UML and Java.

The code samples and anecdotes provide little insight to issues that modern computer engineers need to deal with. The writing is wordy without being precise or complete. The references are antiquated and unimportant. The questions demand only regurgitation, neither thinking nor reflection.

Do not be fooled by the title. No Java in this book. Pretty decent book for software engineering but has only about 2 pages of Java examples/code in it. If you are looking for a book on Software Engineering this may be the book for you but it is an absolute waste otherwise.

I want to read this book on line .Because I am very much like to Object Oriented Books.