5 comments about Microsoft Office Excel 2003 Inside Out (Microsoft Office Excel Inside Out).

1. As with all Inside Out books from Microsoft Press, Excel 2003 was fantastic. The thing I love most about these books is (1) the comprehensiveness of the book while (2) not forgetting to cover the fundamentals of the product. Thus, anything you want to do with Excel is covered, from simple formatting to working with external data all the way up to creating highly complex spreadsheets with macros and programming. This book is perfect for all Excel (or spreadsheet) creators.



2. From what I dicovered from the friend I puchased this book for, she is very delighted with this book because it has ALL the stars & bells she's been looking 4. Thanks alot !!!!



3. I just love these "Inside Out" books for their thoroughness and how well written they are! I'd highly recommend any of the books like this!



4. This book is a great tool and resource for Excel 2003. It provides more detail than MS provided help along with real-world examples. Stinson does another fine job. The included DVD is also a nice bonus. It includes the entire book and is great for traveling without having to carry the book on a plane.



5. This book is absolutely a waste of money if you have been using Excel. I thought since it's "Inside Out", it should include some advanced contents, but I'm very disappointed. I was too lazy to return the book, so I still have it as a decoration.

4 comments about Ethics and Technology: Ethical Issues in an Age of Information and Communication Technology.

1. This book was on the prescribed text list for the masters I am doing (Master of Informaiton Technology) and I must say I was pleasantly surprised to read it. Being a technical (engineer) person, it's a generalized opinion that this group (enclave?) we like mathematics, science and engineering books, but not so called 'arty farty' stuff like philosophy. Speaking for me personally, isn't far from the truth...So I thought...groan, not another one of these idealistic, pointless, ultimately altruistic and futile failures to read. Indeed not! I actually enjoyed reading it! (shock-horror). Tavani uses the ploy of relating his ideas to real-life situations (stalking, cracking, etc). This lends the book a serious air of legitimacy. The ivory tower is nowehere in sight. He doesn't lecture at you like you're a poor, misguided computer geek who could never possibly understand human morals and ethics in a digital world (the point is to help you do that...which Tavani does).
   
   Back to the point: the book builds form the point of view that you have never been exposed to ethics. You get a grounding in ethical theories and then move on to learning how to evaluate ethical issues (kind like logic in mathematics without the symbols). He talks about codes of practice and your moral responsibility as a somebody who works, creates or manages a little corner of cyberspace. It is at this point that the book leaps forward into relevant (if somewhat shallow treatment) of the major issues ike privacy, piracy, crime, security,freedom of speech and equity. These are also posited through scenarios and then the ethics involved are developed through direct discussion of these scenarios. And as I alluded to previously, these give the book an excellent 'hook'. They make the theory real and relevant and rather interesting (and sometimes tragic: you'll see what I mean when you read the first scenario involving a teenage girl stalked thorugh the net and ultimately murdered in realty).
   
   This is a provocative book, but in a subdued, subtle way. The author doesn't speed feed you heaped spoonsfuls of moral outrage with lashings of indignant pontification, just ideas (and these are ever so valuable) in a considered manner. I think the author has really succeeded here. If he can make a totally 'technical' person like me actually enthusiastic about reading it, then that's truly indicative of the book's quality.
   
   The price may be a little high for what is a pretty thin book in a physical sense. Ideaswise it is quite rich, so that's the price you pay (it this ethical? ideas are only available to those who can affort it!) That aside, I got a lot from this little book and so consider it money well spent.
   
   All in all a good 'starting' book for cyberethics! Thumbs up! However consider you may find yourself supplementing it with other braoder, deeper works as you progress because it is a rich field to learn in. Tavani will open this vista up for you if you approch this book with a willingness to put aside your prejudices and listen to what he has to say.



2. It seems that every time you turn around, there's some news story in the industry press about the ethics or legality of some aspect of technology. To help myself understand some of the underlying issues a bit better, I decided to read and review Ethics & Technology: Ethical Issues in an Age of Information and Communication Technology (2nd Edition) by Herman T. Tavani. While not the easiest or most riveting read, I did come away with a better appreciation for the field of ethics.
   
   Contents: Introduction To Cyberethics - Concepts, Perspectives, and Methodological Frameworks; Ethical Concepts and Ethical Theories - Establishing and Justifying a Moral System; Critical Thinking Skills and Logical Arguments - Tools for Evaluating Cyberethics Issues; Professional Ethics, Codes of Conducts, and Moral Responsibility; Privacy and Cyberspace; Security in Cyberspace; Cybercrime and Cyberrelated Crimes; Intellectual Property Disputes in Cyberspace; Regulating Commerce and Speech in Cyberspace; Social Inclusion, The Digital Divide, and the Transformation of Work - The Impact for Class, Race, and Gender; Community and Identity in Cyberspace - Ethical Aspects of Virtual-Reality and Artificial-Intelligence Technologies; Pervasive Computing and Converging Technologies - Ethical Aspects of Ambient Intelligence, Bioinformatics, and Nanocomputing; Glossary; Index
   
   Having never taken a class on ethics or critical thinking, I found the first three chapters interesting. Tavani builds the foundation of how to define and describe cyberethics, as well as how to determine and argue the case of what is "moral". These chapters are a concise course on how to build an argument and support it properly. After those three chapters are done, the concepts that were built are used to examine many different facets of computers and life, and how ethics come into play and shape how we think. There are the subjects you'd expect, like digital rights and security. But he also covers issues that I don't normally think of when dwelling on computers and ethics... gender, socioeconomic classes, race. First you have to determine if indeed those things are ethical issues, and if so, what responsibility do you have in those areas.
   
   On one hand, the book is thorough and detailed. It's meant to be a textbook on the subject, and as such it delivers. These are the types of academic discussions and debates that you'd expect in a formal setting. I was somewhat disappointed, however, when it came to conclusions. Both sides of each issue were debated (even when I didn't even think there *was* another side), but resolution was elusive. I suppose I'm supposed to take this information and draw my own conclusions, but instead I came away with "so everything's right *and* wrong". Since I tend to want to get down to practical issues rather than deal with abstracts, I found it hard to come to any resolution at the end of each chapter.
   
   Definitely good material, and worth reading. But it will make you work and think.



3. While this book would not normally be one that I would purchase to read on its own, it was the textbook for a course on computer ethics that I took and I was pleasantly surprised to find the textbook written in a very approachable matter.
   
   The text starts off with an overview in general ethical theory before starting in to the focus of the text - various issues and how they apply to the growing use of computer technology in the modern world. Some of the topics covered include surveillance, privacy, and file sharing among others. Included with the various issues are up to date examples for recent cases and point/counterpoint perspectives on the topics.
   
   The text does lose some points due to the fact that the last few chapters run a bit thin and could stand to be expanded a bit, but as a whole the text is quite detailed and provides plenty of citations to allow the reader to find attentional information.



4. The book was received very quickly, and it was in excellent condition. This is a great way to save on textbooks for school!

5 comments about Data Structures and Abstractions with Java (2nd Edition) (GOAL Series).

1. Too complicated to use as a tutorial, and too simple to use as a reference. This book tries to be both and does a poor job of it. Buy this book if you absolutely have to (like I did, for a class at the U of MN); otherwise I'm sure there are other books out there that can do a better job.

   P.S. - I found at least one typo in chapter 1. Can you find it? :-)




2. We have been using this book at CSUCI as a textbook for a CS2 class with a heavy hands-on component. The book is very good in that role, and the lab manual - in spite of numerous errors in the first edition - is a very good companion.
   
   It is neither a tutorial nor a reference; it is a textbook for a university-level course. It teaches students how to embed numerous data structures and algorithms in Abstract Data Types (ADTs), how to use them from clients, and how to utilize the existing equivalents from the Java libraries (mainly Java Collection Framework).
   
   I highly recommend this book along with the lab manual to CS2 instructors.



3. This is one of the most useless Java books. I am a professor teaching JAVA in a state university. From my teaching experience and the feedbacks from students, I do not think this work is even worth reading. This book intends to introduce data structure through JAVA programming, but it does not achieve either goal. First, it is not a JAVA introductory book. If you are new to Java, the Just JAVA 2 (by van der Linden) is the best choice. If you want to know more about java, Core Java 2 is the good choice and can also be used as reference. If you want to learn data structure, there are many better books available on pure data structure or data structure with C++.
   
   This book is too expensive for students, and it does not deliver the content that is worth 1/10th of the book price. The only reason I use this for my class is that it is required by University and I cannot change that :(
   
   
   P.S. if you just want to learn more about Java, Think in JAVA is a great book and is free. The author (Bruce Eckel) did a great job in writing a great book and sharing it free on the internet [...].



4. Book was in new condition and shipped within a week. Would do business with again.



5. If you are planning on learning Data Structures and Algorithms, this is definitely the book to avoid!
   
   Concepts are so horribly explained that I've ended up creating an aversion towards them. This book makes easy topics appear to be the most difficult things that you can ever learn.
   
   Mr Carrano may be a top notch Computer Science person, but writing books is definitely not his forte. That is my opinion, after having to deal with this book for about two semesters.
   
   I love books and have read good amount of books on computer science. I usually hate to sell them or give them away , but this book is definitely going to be off my shelf as soon as I am done with my course. In the future, I would for sure avoid any course that requires reading this book.
   No other book bothered (read it as irritated) me as this one did.

5 comments about Programming Windows®, Fifth Edition (Microsoft Programming Series).

1. I have to say I was dissapointed in this book; not because of *how* the material was presented, but because of the *type* of material presented. It says "the definitive guide to the Win32 API" printed right on the cover, but the selection of topics seems limited only to those which deal with output and presentation (text, fonts, graphics, bitmaps, sounds, etc). Personally, i was looking almost exclusivly for the more "under-the-hood" API functions, which almost no mention is made of.
   For example, there is no mention of memory management, manipulating files on the hard disk, serial and parallel ports usage, processes, debugging/kernel, and console-mode functions, just to name a few. Multi-threading, DLL files, and TCP/IP are included at the end, seemlingly only as an afterthought. To give you an idea, the chapter about the "Palette Manager" is over 170 pages long; the chapter on DLL's is only 30.
   Also slightly annoying was the large amount of printed code in the book (my personal pet peeve). Many times, you'll find complete programs that span ten or more pages, with little explanation to accompany them. This seems completly unnecessary, especially considering the stout size of the book to begin with (1500 pages!), and the fact that all the code is included on the CD anyway.
   So if you're looking for a in-depth book about the more 'visual' aspects of Windows, then this could be your book. But if you're looking for more low-level stuff going on behind the scenes, not even one page of this will be worth the shipping you'll pay.



2. This is by far the best book on the windows API, even today is really worth it.



3. I bought this book because MS keeps trying to hide information about how to make basic Windows apps in favor of pushing flavor of the day technologies like MFC and .Net. I remembered that this is the huge tome that all the Windows programmers from the 90s used to lug around so I bought one. I didn't want a book that would allow me to write "hello world" and then leave me stranded. I wanted to be able to port games (or applications) from other platforms in a way that will work across the entire Windows family. I also wanted to be able to make Windows code that could compile with GCC.
   
   If you want to make a simple Windows app, or port a basic app from Linux or Mac to Windows, this book is a key component to doing it quickly, with a minimum of fuss. If you want to make a Windows app using Dev C++ or another open source development kit for Windows, this book is a must have!



4. This book is very well written and the author does a great job explaining every topic that he covers thoroughly. His answers are full of relevant content and he leaves no room for ambiguity. Do take note that this book is dated, but you will not likely find its equal anywhere in its own class of books. If you want to learn about, or become really familiar with the Windows 32 API, this will give you a good reference provided that you refer to msdn for the updated changes to the API which have taken effect since the publication of this book. I won't detail all the helpful topics which are covered as they are already mentioned in other reviews. I had no real problem compiling and running most of the example programs that were contained on the CD included with this book. I used Microsoft Express Visual C++ 2005 and 2008 versions IDE. These IDE's have an option that will convert the syntax for you when applicable. I was not able to compile any of the program examples for chapter 22, Sound and Music. If you are learning to write programs using the Microsoft foundation class library then this book is probably not much help to you. There are other great books available to consider for learning MFC's.



5. This book is worth the price just for the sample software alone. But even more importantant, it is a provides information on programming Microsoft windows that is not available elsewhere. It only covers the Windows 3.1 API, and is somewhat dated. It does not describe the current .NET development, for example. But even if you are a .NET programmer, there are things done here you cannot do there. Microsoft has hidden a lot of their programming features, and this book tells how to unlock them. This is a MUST BUY for any serious Microsoft programmer.

3 comments about Advanced ASP.NET AJAX Server Controls For .NET Framework 3.5 (Microsoft .Net Development Series).

1. I would classify this book as a hardcore, deeply technical look at JavaScript, AJAX, and the Atlas farmework (I am only a few chapters in :) )
   
   The first few chapters I have read so far covered JavaScript more in depth then I think anyone human should ever go with JavaScript but there were some interesting nuances that I didn't previously know about. I haven't got into the meat of the AJAX stuff yet but if the first few chapters are any indication of the depth, this book will be on the "hardcore" level.



2. This book covers literally everything you would ever need to know about using AJAX on the ASP.NET platform. It is full of useful examples. I find my self referring to it quite often.



3. This book has a lot of details. It's hard to just get on with it while reading thru the chapters because the authors seem to think they should try and combine reference material with learning material. Don't get me wrong, I like details, when I need them. However, it is really hard to just do any example in this book without getting bogged down in why rather than how. I think chapter 10 actually starts in on "How", but that's TEN chapters and 500 pages into the book!?!
   
   My other complaint is the vocabulary in this book can sometimes be a complete put off. Instead of saying things like "server side" they say "server-centric" which I guess means the same thing, but why change what everyone is used to saying?
   
   But, the book does have a lot of details and it does belong on your shelf if you want to learn serious ASP.NET AJAX and have a good reference for it. I just don't think it's the book you should read from cover to cover, especially as an intro. Dino Esposito's book is probably a better start.

5 comments about Test Driven: TDD and Acceptance TDD for Java Developers.

1. This book is one of the best books I have ever read. It's easy to understand and well-written. It dives deep into TDD without complicating things, and shows with good examples why you should do TDD.
   
   Highly recommended.



2. "Test Driven" is geared toward Java developers interested in writing better JUnit tests. Despite the title, it is useful whether you want to write test first or test last.
   
   The first part of the book covers the softer aspects of testing such as how to decide what tests to write first and spikes. The rest of the book covers writing tests for common Java components including servlets, data access code and Swing. Examples were for things that we frequently want to test. They included "hard" things such as testing times and threaded code.
   
   I particularly liked the sections on design and testing patterns. There was good coverage of different JUnit extension libraries with examples including dbunit, jmock, easymock, jemmy and abbot. There was also a full chapter on FIT.
   
   I got a sense of "in the trenches" realism from the book. Tradeoffs of techniques were clearing mentioned. The chapter on adopting TDD shows the experience of someone who has done it many times. The section on how to fight resistance really spoke to me.
   
   This is the first book I have read using JUnit 4, which was useful for reading well written tests. While there is an appendix "tutorial" on JUnit 3.8 and 4.0 (two page annotated classes), you really should feel comfortable with one version of JUnit before reading this book. While a few sections pertained to specific technologies, such as Spring, the concepts apply to everyone. I highly recommend this book.



3. Great book. I've read Kent Beck's book, but his book is a bit dated these days. I found Test Driven to be a nice, timely refresh of the TDD and refactoring topic. I've done some mentoring and teaching on TDD and refactoring lately and I've been evangelizing this book to my students/participants. Well worth the money.



4. This book is an great resource for Java developers wanting to get started on TDD. It covers the majority of tools and techniques available, along with useful tips and best practices.
   The first part is already worth the book's price. The author presents TDD and its benefits, shows how it works with a lot of coding, and ends it with an excellent chapter on concepts and unit tests design patterns. By the end of it you'll feel eager to, at least, give the practice a shot.
   The book proceeds showing how to test technologies commonly known as "hard" to unit test, like web components, database access code, threads, and swing. Although the author doesn't go into too much detail in any of them, he presents good solutions to make their testing easier.
   The last part is a very good introduction to Acceptance TDD and how to write tests with Fit. It is not as thorough as the TDD introduction, but will give you a very good understanding of what ATDD is, how it should be done and how it can (and should) be complemented with unit testing.
   Essential reading for Java developers looking for ways to improve the quality of their code.



5. Bas has already done a good job outlining the content. I won't repeat that here. Instead I will say that TDD is hard. It took me several years of trying before it all came to together for. In the past few months I've recommended this book to more than a few developers in the past six months.
   
   In at least two of those cases it has been the turning point in their understanding of Test Driven Development. Net result - I'm can spending my time coaching/mentoring in other areas.

5 comments about Java How to Program (6th Edition) (How to Program (Deitel)).

1. The book provides many visual examples that help audience to absorb the concepts easier, still we need to reference Sun Java website' API though. Concepts of Object-Oriented Programming, GUI, Data Structures, Sorting & Searching, and among other basics are covered in relatively brief but clear. I think those are enough for beginners who take Java as their first course, as its purpose. The later chapters sparsely introduce more advanced features in Java such as Networking, Web Applications, Database with JDBC, JAX-WS Web Services, etc... without giving complete explanations, as if they are reluctantly added to the book to make it looked thicker and heavier. If you are a beginner, you might not need to cover these features, but if you are going to advance, you might likely encounter dead-ends or summarily discussions.



2. I wish I had started Java programming with this book. It's written for those who prefer a thorough and methodical learning approach (less "whimiscal" than "Head First Java" and less "philosophical" than "Thinking In Java". The book covers general programming and basic Java language concepts. It is long but not lengthy. The book teaches practical programming skills in a no-nonsense fashion. You can learn Java from the ground up with this book and the free Java tutorials and JDK/API from the Sun website. I already work with Java for some time, so I did not learn anything new from this book, but I still appreciate the didactic approach. The only thing I found annoying is that each and every code example (which are excellent by the way) is explained tediously in natural language. This adds bulk to the book and is IMO unnecessary, because the code is self-explanatory. Hence, four stars instead of five.



3. JAVA HOW TO PROGRAM 6TH EDITION
   If you are serious about learning Java, then you must have this book.
   This book is a comprehensive study of Java.
   You have to read each line carefully and do the exercises. You will have to go back to many sectioins that you studied already in this book and read it again. At some points, I decided to go to other books that might make it easier for me to learn Java, but I always go back to this book.
   The book has a large variety of examples and exercises. When you finish
   this book, don't get rid of it. You will need it when you are writing
   Java Code.



4. Pros:
   =====
   Good material. Great organization. Good examples. In Color. Love the writing style.
   
   Cons:
   =====
   Print is to small. This should possibly be spilt into Vol 1 & 2 or the format enlarged to make the material more readable. Yes, I know it would cost more but the additional paper would be worth the cost.



5. nice book. EASY TO UNDERSTAND / FOR LEARNING THE BASICS.
   
   FOR BEST RESULTS, USE WITH AN ONLINE REFERENCE WEBSITE.
   
   YOU`LL BE FINE

5 comments about Hackers and Painters: Big Ideas from the Computer Age.

1. I was entertained and greatly appreciated the view of the author but the many times I completely disagreed (due to very substantiated reasons) made me skeptical of several ideas of the author. But, the reasons for him holding those views is, in and of itself, interesting. He does have several good and controversial ideas and his experiences are quite valuable to read. Most of the time, I found myself flying high with him as he stated things that really need to be said which ran against conventional thought. Other times, I found myself raising my eyebrows in bewilderment. After all, it really is a book about his thoughts so take it as such. His book, his soapbox.
   
   The book reads well but really trails off towards the end. I found myself finishing the book just so I could say I was through with it. The opening chapters are quite entertaining. Read a few chapters that you find interesting and leave it at that.



2. In spite of the strong desire to punch the author in the face after finishing the book, there are many great truths inside. Basically why is it that most people think salaries on the same position should be the same if work results differ in orders of magnitude.
   
   Also it's funny to see an ultra-capitalist criticize the western decadent corporate structure. It's The Market for Lemons all over the place.
   
   Don't expect to find anything useful to make a dot com startup on this book. It's all anecdotes from his experience and his quasi-religious views. It's more rhetoric on Lisp than business.
   
   As another reviewer said, read first his online essays before diving into this.



3. Paul Graham is very clever (and rich - is that relevant?), however light also bends around his ego. Whether the sum of these qualities is positive is not absolutely clear to me.
   
   If you want to read the best thing that he has written, you might be better served by his book on advanced Lisp programming, which is a monument anybody can be proud of - it comes close behind SICP on my personal list.
   
   And, if you do read this book, I suggest you also look at 'The Science of Art' by Martin Kemp, which gives another perspective on the maybe slightly overweighted metaphor of the title, and the relation between theory and practice it implies.



4. The book particularly deals with the nexus between programming, creativity, social commentary, wealth-generation, business-personal-entrepreneurial psychology (his specialty!) and LISP-related stuff. I skipped the programming sections because Im not a programmer. The philosophical commentary was better than 90% of other philosophy books I've read, more cutting and more true-to-life.



5. Hackers and Painters is a good read. I enjoyed learning about the author's perspective on programming trends. I really enjoyed learning about his enthusiasm for Lisp. This book is not a how-to, but a collection of essays describing the authors views, opinions, and experiences with various programming topics. I definitely recommend it.

3 comments about Managing Software Requirements: A Use Case Approach (2nd Edition) (Addison-Wesley Object Technology Series).

1. I'm quite surprised to be the first reviewer of the second edition of this book since it ia a reference in requirements management.
   
   After, but even during, reading this book you perceive that it's a sum up of their vast, deep and long experience. The authors are the implementors of RequisitePro the tool, now part of the Rational Suite, for requirements management, but this book is not a promo. Instead the whole process of gathering, organizing, and connecting (to following steps in the process) requirements is presented. It's clear to them that basically you have to collect the clouded needs of the stakeholders and formalize them in a set of documents that you have to give to the development team. And the entire process should effectively work, managing change.
   
   After introductory chapters, you are presented with six skills a requisite team shoud have to effectively manage requrements and each skill is expressed, through different chapters, with what needs to be done and what needs to be produced.
   
   I especially reccommend team skill 6 'Building the Right System' because in those chapters you find how to connect use cases to design (chapter 25), how to generate test cases from use cases (chapter 26), traceability techniques and tool from user needs to code (chapter 27). Besides this, team skill 4 'Managing scope'.
   
   Don't forget to read chapter 30 that illustrates and compares extreme, agile, and roubust requirements gathering methodologies, and chapter 31 that sums up all the steps illustrated in the book, suggesting a methodology for requirements gathering based on the kind of project.
   
   In the appendix you find chapters with the whole results of the case study (HOLIS), the detailed template of basic and fundamental documents for software requirements management, and, above all, two chapters one that is a brief presentation of RUP and another that is an indication on how to link the process so far developed to SEI-CMM and ISO 9000:2000.
   
   Another useful feature is the fact that every concept is illustrated with a simple,visual example (in visual modeling philosophy) that allows you to impress the concept in mind. At the end you come out with all the concepts you found (even from different sources, but unrelated) with the big picture.
   This is my first book on software requirements but it has many pros and only one con. It's a recent book that is aware of the state-of-the-art in managing software requirements (see bibliography), and I'm sure that other books in this field can't be overwhelmingly better. The only con, that is easily resolvable, is that the documents illustrated could have been included in a CD with the book.



2. Being in the software industry for about 10 years, I had known that our teams often did a poor job of managing, gathering, and understanding requirements. Our projects suffered because of this, and despite my gut instincts we were going the wrong direction, I often felt that I didn't have statistics and the insight to counter some of the more experienced staff or management. This book greatly has changed that as now I can come in armed with info and present better ways to improve our requirements management. I now feel that we'll deliver the right product or system instead of breaking the hearts of our customer and our own team members (because we won't be failing!). The authors also write in a very clear manner and provide excellent examples. I can't believe I am writing this about a requirements book, but I found myself actually _looking forward_ to reading each chapter. I am now confident I have the tools we need to sucessfully manage requirements. Thanks for a great book!



3. I had the pleasure of speaking with the author (Don Widrig) over the phone prior to a job interview and he helped close the loop on some of the concepts presented in the book. I went into this book not knowing that use cases are used in the requirements analysis phase because honestly, I never did that phase properly and even my masters level courses didn't provide this information.
   
   The book outlines the proper steps to gathering requirements from a use case perspective and provides numerous examples that you can actually apply in the real world. I would definitely recommend this book to any systems engineer, business analyst and even people interested in understanding process mapping more.

5 comments about UML 2 Certification Guide: Fundamental & Intermediate Exams (The MK/OMG Press).

1. I passed the Fundamental exam with a score of 66/80 using this book exclusively. It is very concise and to the point. It has 34 practice questions in the back that help you prepare for the Fundamental exam. The questions are similar to the real exam questions. There are no practice questions for the Intermediate exam. I am now using this book to prepare for the Intermediate exam.



2. Good book to have for UML Certification...I wish every UML evangalist must have for reference.



3. This is a good book for preparing to the OMG UML exam. Each one of the most important elements of the UML metamodel are treated with a simplified view.
   
   The sample exam of the end is so useful. I recommend the book.



4. Before buying this book, I had no doubt that it would be instrumental in passing my certification exams. I did pass the the Fundamental exam in the first try itself and I don't believe I would've been able to do so if I had not laid hands on this material. Neither do I think there's a book out there that covers UML with the level of detail as this one does. After all, this guide is published by the same Group that sets the UML standards and administers the certification program! I'll be referring back to it again for my Intermediate-level exam. Thanks OMG!



5. Really complete book, clear and concise. It's a very good tool to pass both of the exams, as well it's a great resource for those who want to initiate and work with UML.