Customer Reviews

Beginning Java Objects: From Concepts to Code

5 star:		(70)
4 star:		(10)
3 star:		(4)
2 star:		(1)
1 star:		(2)

 

 

When people who have not previously done object-oriented programming begin to learn Java, my experience has been that they mistakenly assume that learning the language itself is the only thing that they need to do. In reality, the most important thing (and in my opinion most difficult) is to learn how to create a good object-oriented design. Before they can create a good design, they need to understand object-oriented concepts and the tools that are available to them such as UML. Jacquie's book does an excellent job of introducing the reader to those concepts and explaining them clearly. It has been said that you cannot explain something well to another person unless you really understand it yourself. If that is the case, Ms. Barker clearly understands object design very well.

If you are learning Java or considering learning Java for the first time, I recommend reading these books in the following order:

Beginning Java 2 (Ivor Horton)

Professional Java Programming (Brett Spell)

Beginning Java Objects (Jacquie Barker)

These three Wrox titles complement one another very well, and are all well-written and easy to understand.

In reading Barker's title, one gets an extraordinarily good education into the major considerations for object-oriented design. Although the book's title would imply that Java developers would benefit most, this is a great introductory manual to OOP and Java 2, and perfectly suited for other platforms, as well.

It's actually a very helpful, very educational, very entertaining look at object-oriented software design, at modeling, and at proper management of the process in which they are used to create great software applications.

Barker does a fantastic job of describing the process and life-cycle involved with designing and coding a system, and centers the concepts presented around an iterative practical application, a student registration system for college. She also bases her method of teaching concepts-first-and-then-code around pseudocode, so the reader isn't inundated by too much syntax while trying to grasp fundamental subjects. Barker also steps the reader through the procedural methods of designing an application, such as creating a vision document and glossary of system-specific terms.

In doing so, Barker also uses one of the friendliest voices in her writing that's truly a rarity in technical books these days.

Being an ASP.NET developer working almost exclusively in C#, I got a lot out of it. The Java syntax might be a stretch for VB devs; the book also makes for great recommended reading for those just starting to get into OOP or Java. I'd also recommend this book for Microsoft developers migrating up from Windows DNA and ASP 3.0 technologies, as it really does a good job of walking you through OOP/OOD, which in my opinion has proven to be THE major hurdle for many devs in embracing .NET.

The only downside I can see about this book is that because of the title, developers non-Java other platforms and disciplines will unfairly look past it, and therefore miss out on the important lessons contained within its pages. The book's key strength lies in the chapters on designing use case scenarios and UML diagrams, which I really enjoyed.

It's these unexpected advantages that have put this book in a prominent place in my home library that keep it easily within reach.

Being new to programming, and wanting to get off to a good start, I agonized over which book to begin with. Should I start with Deitel's "Java: How to Program?" Or how about Horton's "Beginning Java 2"? Or maybe Schildt's entry level java text? It was all so confusing! Then I happened upon this excellent book, and I knew immediately that this was the one.

Let's face it, in today's programming world the OO paradigm is where it's at. Unfortunately, however, many introductory books focus on code first and object oriented thinking second. This is completely wrong!

As children, we learn the concepts of words first, and then later, in school, we learn how to properly organize those concepts into prose. Should it be any different in learning a programming language? I think not.

The fact is that one must have a solid understanding of the object oriented paradigm before one can really be an effective programmer, and this book provides the reader with just such an understanding. It is very readable--fascinating, even--and will allow one to better understand what the many fine "introductory" java books such as those mentioned above are really taking about.

The book is divided into three parts -- object oriented principles, object modeling, and Java. The author introduces objects and modeling first and then moves into Java.

You may think that you have enough to do just learning Java without facing design and modeling issues. You may think that you may be better served by concentrating on just the Java language and turning to OOP, UML and the rest of the alphabet later. Well, no.

Many Java texts cover language syntax and features, but you never learn what to do with the language after you have learned its syntax and features. You get to the end of the book and all you are capable of doing is writing toy applications -- like the sample code in the book. Oh, boy, some fun, rather like memorizing your ABCs and never learning to read.

Java Objects avoids this problem. First, the objects-first structure provides the reader with a context into which to place the language features that are covered later in the book. It certainly made sense to this reader to learn why you might want a "class" before delving into the details of a Java class.

Second, the author uses a long, single, unified sample application throughout the book to demonstrate object oriented programming and Java. She does not bounce the reader from toy application to toy application with the introduction of each new language feature. The use of a single sample application really helps pull principles, modeling and language together.

The book is well written and carefully edited, but more important, the book was written by someone who is a gifted teacher. I don't know how she thought of helium balloons to explain object references, but I'll never wonder about references, pointers, or handles again.

I got this book from reading the user recomendations here. I just want to warn people this book is about 900 pages long, and the whole book goes into making just one program (a student registration program for a university). If you have the patience to read a book like this, fine, but for me its a little too drawn out, and nothing I saw thumbing through the chapters jumped out as being interesting or trying to make a point. I have read "Head First Java" and recommend that book for someone who is trying to make sense of OOP.

Edit: I want to update this review by saying that I was too rash in critisizing this book. This book does do a good job of explaining how to plan and organize object oriented constructs to address real world problems rather than just a nuts and bolts overview of OO syntax that most other Java books give. This book however is not a "how to program in Java" book. You are going to have to move on to other Java books to become proficient in coding.

Always thought of JAVA as intimidating, yet wanted it on you resume? And Object oriented design, why is it so complex and roundabout after all? Obviously, you need to try this brand new book written in a fluid, easy going manner, with real life examples. It starts with the basics of objects, leads you through the design phase, and maintains your attention with realistic and easy to understand figures. All the while, a contant effort is made to relate it to JAVA and C++, and helpfully, a distinction is made between these two most popular languages wherever necessary. It is a must read if you want to take your JAVA seriously.

New to Object Oriented Programming? New to Java? Read a beginners Java book but confused? Can't quite grasp OOP or Java? Then buy this book NOW!

This book is absolute essential reading for ALL Java newbies. Do not purchase a beginning Java book without buying this book as well. It is the PERFECT compliment to any beginner Java book.

The author takes you by the hand and babysteps you though the basic and advanced skills of object oriented design. I read Ivor Horton's "Beginning Java 2" and was quite confused, then I read "Beginning Java Objects" and ALL my confusions disappeared. As someone in the bible said, "I was blind and now I can see."

Do your self a favor and pick-up this book right away!!

When I decided to buy this book, I wasn't sure if it was for me because I have no experience (and I mean it) on computer languages and programming. I started reading it and I understood everything so well because she explains all the small details and mentions some very useful examples. I have only read the first chapters, but I'm learning a lot. Now I'm going to take a Java course at my university and I feel so confident about it. I understand the most important features of the language and I know I'll do a very good job in my class. I recommend this book to anyone who wants to learn Java and has no programming experience at all, or even if you just want to learn about OOP (Object-oriented languages), this book is definitely for you. Buy it, you won't regret it! I didn't!

Having tried to master Java before, I found that all of the books I consulted taught Java syntax without really explaining how to structure an application around objects so as to truly leverage Java's power as an OO language.  This book accomplishes what no other book, to my knowledge, even attempts to do:  that is, to step through a case study from beginning to end, illustrating first how to think from the perspective of objects, then how to model the application using UML, and finally, how to translate the model into working Java code.  It is, in my opinion, a 'must read' for anyone striving to become an accomplished Java designer and developer.

I had the first edition of Beginning Java Objects From Concepts to Code sitting on my bookshelf for about 4 years. Meanwhile, I've taken several different Java training courses ranging from beginner to advanced level. I've been part of a development team, and although my role has generally been more of a business subject matter expert, I have also gotten my hands dirty and done some large chunks of coding, debugging, and refactoring other people's code.

So what's my point? Well, although I've gotten by well enough in a pretty intense OO/Java environment, I've always felt like it was exactly that - getting by. I finally took this book off the shelf and worked my way through ALL of it over the last couple of weeks, and it really pulled things together for me in a way that nothing else has done. I've read about half of Eckel's Thinking in Java (a couple of times), and most of Deitel's Java How to Program, among others, and they're really great at what they do, but I wish I had worked through ALL of this book before (or at the same time as) reading those. Even though I already had a good understanding of Java syntax, this book helped me understand more than just the syntax of "System.out.println()".

I've seen a couple of reviewers comment on Jacquie Barker's friendly tone, and I certainly agree with those reviewers. I felt like she was a trusted colleague helping me along, but not talking down at all.