5 comments about The Unified Modeling Language Reference Manual (2nd Edition) (The Addison-Wesley Object Technology Series).

1. This book is one in a series of three by the three amigos. It is certainly the most authoritative and accurate of all three (the other two being very fuzzy in places). The book consists of the following major sections:

   I: Background (some history) II: UML concepts (static, use case, statechart and other 'views') III: Reference

   This book is pure syntax and can answer most of the questions that you might have about UML syntax. However, this book is not for beginners because it assumes (in my opinion) that you have applied UML to real-life situations. I find the book to be well-written (even if it is fairly dry) and compares favouably with other books in the UML series. There are different ways that you can use this book. First, you can consult it to check of you are using the correct UML syntax in your applications. Second, you can use it to deteremine what you have still to learn in UML (for example, activity diagrams, statecharts). This book should complement the other, more application-specific UML books. For example, it could be seen as a follow-up of Fowler's somewhat outdated UML Primer.

   It would have been a good idea if the authors had included a complete test case showing how all the specific 'views' are documented and how they fit together. UML has about 11 different views and which one to use and when will be a major undertaking if you are embarking on a first project.

   This book will be outdated as soon as the new UML 2.0 specification is ready. Do the authors have plans for a new version of their book "UML Reference 2.0"?




2. This book is too theorectical. Needs to elucidate for readers with examples. Unless you are an UML professor or an abstract UML guru, this book does not help to learn UML. Would help if authors shows UML mapping to say, C++ and Java.



3. I do a lot of UML modelling, and I keep this book by my desk at all times. It has in-depth information, is well-written, and is well-organized.

   The Reference Manual and the Users Guide are generally sold as a pair. Quite frankly, if you have the Reference Manual, then you don't need the Users Guide.

   If you are just learning UML and are already familiar with any formal design methodologies, then you can do just fine with the Reference Manual alone. However, if you are new to graphical modeling in general, you may want to buy "UML for Dummies" to serve as a useful introduction.




4. This isn't something that I would sit down and read just for fun, but it is well written and organized, which makes it easy to use. The bulk of the book is in the dictionary of terms which is organized alphabetically. Each one is described using both a text definition and a notational graphic, and often an example. There is a section on the different types of views at the front of the book.



5. Like all dynamic languages, the Unified Modeling Language (UML) is growing more complex over time. While it is true that for most developers, this means that you will regularly use a smaller percentage of the language, the actual percentage will vary from person to person and from day to day. Therefore, no abridged UML manual could possibly be adequate. Written by the three creators of the UML, this manual is clearly definitive and one that all developers should have at extended arms reach. Designed to cover the changes in the recently released UML 2.0, which were significant, a CD with the full text in Adobe PDF form with hotlinks to the definitions of the key terms is also included.
   The opening chapter is an overview of the UML and most people can skip it. Chapter two is an overview of models, and this one is worth reading. Short, it introduces some of the fundamental terminology and approaches. A walkthrough of UML is done in chapter three, which introduces the various formal views of a project. They are: static, design, use case, state machine, activity, interaction, deployment, and model management. Each of these views is then explained in a short chapter. These chapters should be required reading for users of the book, as they establish much of the notational and definitional background used in the reference section.
   The real value of the book is in the five hundred plus pages of detailed definitions of the key terms and phrases in the UML. Listed in alphabetical order, each entry has the following form:
   
   *) Entry name: the term or phrase.
   *) A brief definition, generally one or two sentences.
   *) The semantics of the term, generally using several paragraphs. This section Includes the structure,
   subordinate items and often an example.
   *) The notation of usage. Options and guidelines for use are often included.
   *) Discussion (occasional), where the author's opinions and/or a background explanation of the term
   are given.
   *) History (where appropriate), the changes in how the term is interpreted from earlier versions of the
   UML.
   
   Quite frankly, I cannot see how it would be possible for any developer to use anything more than a very tiny subset of the UML if they do not have access to this book. All speakers of a language can use that language in informal communication, but when we want to communicate ideas formally and precisely, a dictionary is essential. That is the role that this book will fill, as no human communication is more precise than when we do it with notations that describe software.
   
   Published in the online Journal of Object Technology, reprinted with permission.

3 comments about Mastering Visual Studio .NET.

1. The book deals with mostly an overview of VS .Net features. They give a general guideline on how to write VS solutions / projects - components - scripts, amd how to debug programs. I bought the book mostly since it's the only one I found that discusses VSIP. I did not find a lot of information on VSIP 7 pages long chapter which barly discusses an overview. The book authors tried their samples on both VS 2002 and VS 2003. I would not recommend this book to people who are brand new VS users or experts on VS. I would recommend it for some users how are looking for some extra shortcuts / functionality here and there. I'm giving this book 3 stars since I would have expected a bit more in debth analysis and more samples.



2. I have to admit that when I picked up a copy of this book, I was expecting a rather out of date re-hash of much of Microsoft's Visual Studio documentation. I was pleasantly surprised. Even though Visual Studio .NET 2003 only recently became commercially available, this book is written for the new IDE (rather than last year's model). The book goes through the basics of projects, debugging, and even macros (in addition to a wide range of other topics).

   This book follows the basic flow a programmer would follow when setting up and creating a project in Visual Studio, which makes it easy to follow along (especially if you are new to VS.NET). After a discussion on setting up a project (including the differences between the various project types), the reader is presented with a discussion on debugging tips and techniques (including debugging configuration in the project's properties). Since web projects are a little different from creating a Windows application, there is a whole chapter dedicated to configuration and debugging of a web application. Other chapters include a discussion on how to perform database work through the IDE, and instructions on developing installation projects.

   My absolute favorite chapter, however, was on Automation, Macros, and Add-ins. In this chapter, the reader learns the basics of creating macros that integrate directly into VS.NET. If you are familiar with recording macros in the Microsoft Office applications, you will be pleased to learn that the syntax and functionality is similar (although instead of writing macros in VBA, they are written in VB.NET). There is then further discussion on automating the IDE to perform scheduled tasks (like automated builds).




3. It covers many topics around Visual Studio.net. Its coverage of Debugging(Chap 3), Macros(Chap 8) are good.

   One missing piece is Web Services with Visual Studio.net. I didn't find any related information in it. Also, serveral times, when I needed some information about Visual Studio.net, I couldn't find it in this book. Though I've been using VS.net for several months, I never needed most of the information in this book.

5 comments about Flash 8 Essentials.

1. I recently finished reading Flash 8 Essentials, and have found it to be an excellent resource for anyone looking to jump with both feet into the complex world of Flash design. The contributing authors are some of the biggest names in Flash design today. There is so much packed into this book that I am only going to be able to touch briefly on most of the highlights. Of the many new features available in Flash 8, here are the ones I found most exciting:
   
   * Search Engine Compatibility
   * Graphics Effects Filters
   * On2 VP6 Video Codec
   * Improved Text Rendering
   * Bitmap Caching
   
   Each of these topics is covered at length throughout the book. What's especially nice is that source code for each example can be downloaded from the website. You don't need to have purchased the book to use these code examples, but they will of course make better sense when accompanied by the text. Without further ado, here is why each of these improvements really matters...
   
   ch.1 - Search Engine Compatibility
   
   This book refers to this momentarily, but I thought it important to mention. One of the biggest complaints against Flash is its lack of accessibility, and implicitly its lack of search engine friendliness. These issues have been put to rest with Flash 8, because it now supports using a version of XML entitled XMP, which stands for Extensible Metadata Platform. In short, this means that Flash can now comply with W3C standards for information accessibility.
   
   This metadata could probably double for usage in subtitles, to aid in viewing Flash movies for those who have hearing impairments. For a good example of this in action, check out the Making of Flash 8. Throughout the video, by using various keypoints the way one would index DVD chapters, there are changes in the text displayed along the bottom of the screen.
   
   Stored as metadata, this could be indexed by Google, and would increase page relevance for the topics covered throughout the video. I never thought the day would come that I would use the word accessibility in reference to Flash, but I think that if designers pick up on this, it will be beneficial to the hearing impaired, as well as your clients. It's smart on both sides of the argument.
   
   ch.3 - Graphics Effects Filters
   
   In the past, if you wanted to have an effect added to something in your animation, it was not an easy thing to do. For instance, if you wanted to include a drop-shadow, you would have to make it ahead of time in a graphics program, and then import it as a layer into your SWF file. Flash 8 though, can create drop-shadow effects from within the player. These effects can even be created live via ActionScript, Flash's language similar in syntax to JavaScript.
   
   In fact, all effects and filters can be manipulated via ActionScript. These include the following blending modes: Normal, Darken, Multiply, Lighten, Screen, Overlay, Hard Light, Add, Subtract, Difference, Invert, Layer, Alpha and Erase. Various available effects are: Drop Shadow, Blur, Glow, Bevel, Gradient Glow / Bevel, Adjust Color / Matrix, Displacement Map and Convolution.
   
   Photoshop users will no doubt recognize many of those, and immediately realize the benefit of being able to call these into effect during runtime rather than constantly importing multiple PNG images. If those don't sound familiar then buy the book. I can't just give away everything - This ain't no hand-out!
   
   ch.5 - On2 VP6 Video Codec
   
   Another thing I'm all fired up about is Flash's great new handling of video. Gone is the trusty Sorensen Spark codec, although it still remains as a legacy option. This paves the way for the new On2 VP6 Codec. On2 codecs are also being used in other popular products such as the new Skype video beta.
   
   What this means for Flash is new support for alpha channels within video. For instance, in the fight between Anakin and Obi-Wan in Star Wars Episode III, very little of the surrounding environment were actual props or movie set. Most of it was shot against a green screen, after which the green areas were replaced with digital enhancement. This is now possible to do with Flash.
   
   Also new are the embedded cue points, making subtitles via XML a possibility. Also, with Flash 8 Professional there is a stand-alone video encoder which allows for massive batch file processing. So, if you are a video guru and work in Quicktime format all day, and need to convert many of those MOV over to FLV files, you can batch convert them all overnight, rather than one by one.
   
   ch.6 - Improved Text Rendering
   
   A huge complaint of Flash has always been that text below a certain point size, depending on the font, becomes nearly unreadable. To get around this, many designers would purchase pixel fonts made especially for small scale display. Communities such as Fonts for Flash arose to compensate for this deficiency.
   
   Printed text aficionados can rejoice, because Flash text rendering just got a huge shot in the arm. It's called Saffron, a technology that has been licensed from Mitsubishi Electric Research Labs. It works similarly to Microsoft's ClearType in Windows XP, or the native font smoothing of Apple OSX. Flash pushes Saffron to the edge, with several modes for readability, animation or even custom settings. It nearly allows for creating entirely new font faces.
   
   ch.7 - Bitmap Caching
   
   In the past, if you had multiple vector shapes viewable at once, the Flash player would have to render each and every animation on the fly, increasing strain on the CPU with each additional graphic. Version 8 though, allows for caching of shapes that might animate, but not change. For instance, if a square-shaped object is moving but not rotating, it can be cached as a bitmap.
   
   If it were to rotate slightly, then the rendering engine would need to redraw it, after which it could be cached again as a bitmap until the next rotation. You can think of it this way: Distortions such as rotation, changes in opacity, and zooming - all require re-drawing. Simple things like moving an object from left to right can be cached. This allows Flash Player 8 to be the fastest ever. It should be noted though, that caching should be enabled wisely, because if you are constantly misusing it, it actually increases strain on computer hardware.
   
   Summary: If you're looking for a great place to get a handle on the new improvements in Flash 8, this book is for you. If you don't have a background in previous versions such as MX 2004, you might want to consider Foundation Flash 8, which covers more of the basics.



2. Notice how long the reviews for this book are? Why?
   Because this book is fabulous, not just good, and it is filled with an impressive array of really useful material.
   As one who is self taught in flash, books are my instructors and this one is great.
   It gets right to the point with exactly the stuff you wanna know, which is, what is new in Flash 8.
   This book clearly and methodically explains it all, chapter by chapter.
   It is NOT a sequential build-a-project step by step book.
   You can jump in at any point.
   
   If you want to know about the new bitmap data class just read Chapter 8. Blending modes? Chapter 2. The on2VP6 codec or the new video alpha channel support? Chapter 5.
   And if you don't want to be in the dark about the new filters, just read chapter 3.
   Simple as that. This book gives an excellent description with lots of pictures demonstrating visually what does what. Considering the complex subject matter, this book is amazingly easy to take in.
   
   The tutorials included in the chapters are both facinating and fun. At the end of the book there are 3 examples to help you get indoctrinated to the new elements of Flash that this book has laid out. You can download the fla's from friendsofed.com. They are well chosen and well thought out.
   
   The action script used throughout the book is navigable, makes sense and is logical.
   Sweet! I can understand what it means, thanks to the fine work of the authors. That is what really makes this book so special, here you have 6 different authors each with great presentations.
   I originally borrowed this book from my Flash user group library but now that I have to return it, I realize I can't live without it so I'm here to buy it. It can be excellent for use as a reference book after you read it. I highly recomend this book.



3. With Flash 8, Macromedia (now Adobe) gave veteran Flash Developers a wealth of new creative options to explore. Many of the features, while clearly powerful, are not intuitive to use. This fact is primarily due to the inherent complexity of the new tools. Filters and gradient focal points are not as easy to figure out as the basic timeline and drawing tools. And trial and error is simply not going to lead you to a solid of understanding of how to use External Interface to communicate with JavaScript, or what the Cache As Bitmap setting does. Unfortunately, the documentation within Flash is a bit thin so most users have to resort to scouring the internet for tutorials and tips.
   
   This is where Flash 8 Essentials comes to the rescue. The book provides documentation of all the new features in Flash 8 (and only Flash 8). This is not a Flash for Beginners book. It is targeted squarely at experienced Flash artists and programmers who want to tap the power of the new features. A better title for the book would have been "What's New In Flash 8".
   
   Each chapter focuses on a particular feature, and there is little overlap, so you can jump around to the parts that are most pertinent to you. Chapters are organized with the less technical information at the start, and more complicated bits, including the ActionScript, at the end. In this way, the book can be useful to both artists and developers, and it's easy to figure out where to go for the information you need.
   
   I was a bit leery at first, when I saw there were 6 authors attached to the book. Fortunately, the editors at FriendsOfEd successfully pulled the content together, and made it feel consistent. I also tend to avoid computer books like this one with lots of pretty color pictures. However, in this case, I feel the color is a necessary component of the book because pictures are the best way to demonstrate different filters and blending modes. And I have to admit it's definitely a nice-looking book.
   
   If there's one part that feels thin, it's the chapter on Video. I still don't have a solid understanding of the "new ON2 VP6 codec", (though the authors dropped this buzzword many times). Granted, Flash Video probably deserves a book of its own...
   
   In short, Flash 8 Essentials serves as a manual for veteran Flash developers who want to get up do speed on the new version. It's too bad the software makers no longer ship adequate documentation with their products, but I suppose we should be glad that companies like FriendsOfEd are around to fill the void. Adobe would do well to include a copy of this book with every upgrade version of Flash they sold.
   
   Disclaimer: I was given a free copy of this book for review.



4. I just got into Flash and after reading Phillip Kerman's Flash 8 in 24 Hrs, i really wanted to get even more into it. This book is for me like the title reads "Essential". The explanations and lessons are fantastic and eye opening. This book will be on my desk at all times as i journey though the fantastic world of Flash 8 Pro!



5. This book is good for experienced flashers who want to play around with all of Flash 8 cool new features. Shows you how to use the new filters and blends in both the IDE and actionscript. Full color examples and useful sample code.
   
   Definetly pick this one up if you want to exploit the power of Flash 8.

5 comments about AspectJ in Action: Practical Aspect-Oriented Programming.

1. I have got this book at local Austin Java User Group meeting. First impression: different cover. Most of Manning books are either greenish or almost black-and-white. This one is yellow.

   Part 1 provides really good introduction into AOP. This is the first book I have read on AOP; all stuff I have seen before was online or magazine articles. One interesting fact is that this book took a while to consume, compared to the usual two-week cycle I have for technical books. I guess the reason is that the book has more substance than most of the techincal books and Mannigs does not try to pad their books with API references and other stuff that can be easily found online. After the chapter goes through AOP concepts, it explains AspectJ in application to those concepts. Basic syntax as well as some advanced techniques are explained.

   Part 2 has examples of basic applications of AspectJ. Of course it starts with the mandatory logging implemented using AOP. Not a very good example in general, since logging is not really a cross-cutting concern, but works for illustration purposes. Other two application areas discussed in this part are implementation policy enforcement and optimization (pooling and caching examples). Policy enorcement part is really interesting, especially if you are into call patterns.

   In general, every part follows the same pattern: first the author discusses the conventional approach, then explains challenges of the conventional solution, provides AspectJ-based solution, and gives one or two examples. Very clean language, easy to follow.

   Part 3 discusses advanced applications of AspectJ. First it delves into design patterns and idioms of AOP; it's not by any means AspectJ-specific, so would be useful for any AOP implementation. Examples of patterns are providing thread-safe implementations using AspectJ, implementing security (very interesting discussion on JAAS), transaction management, and implementing business rules using AspectJ. The part ends with AspectJ usage in different development phases.

   Two appendices: description of AspectJ compiler and Ant integration - only 15 pages for both. Useful as a reference.

   Overall impression: an excellent book. Definitely worth reading, even if you are not into AOP yet.




2. I met the author of this book this weekend, and saw him give a presentation on this material. Finally, a book that shows real uses for AOP.
   I have been watching AspectJ since I first saw it about a year ago. My first impression was that it was 'cool', but was worried about giving developers more rope with which to hang themselves. Yes, it was cool, but the most practical examples you would see in demos were thing like 'logging'. I was worried that it would just lead more more ways for junior engineers to 'convolute the code', without bringing much benefit for that risk.
   The material in this book, ALONG WITH the support the author had from the Eclipse IDE changed my mind. Finally, there were some real examples involving transaction support, JAAS, exception handling, and more. Furthermore, he addressed these topics in the real-world sense of refactoring existing code to prove his points.
   If you aren't using an IDE that gives you some support, then I still have my concerns about 'convoluting' your code; but I am more convinced than ever that AOP concepts are worth putting into my mental toolkit. I have no doubt that the way aspects 'inject' behavior into code will reduce our development time, and make our code behave more consistently (no errors because of inconsistencies in the way common things are handled). If you can add one more ball to the things you 'mentally juggle' while developing, add AOP concepts. This book will help.



3. AspectJ In Action is a great book to use as an introduction to Aspect-oriented Programming. However, AOP is not for developers to whom Java and OO are still new. Without a comfortable understanding of classes, polymorphism, and encapsulation AOP will only further confuse things.
   
   With that said, AspectJ In Action is a wonderful book filled with plenty of examples and explanations about the well-lit areas of AOP as well as many of the dark corners. I enjoyed reading this book because it starts out with the fundamentals and works its way to more and more complex uses of AOP without getting bogged down in language tangents. Also, the direct application of AOP in real Java design areas is very helpful in getting a better feel for when and how AOP can be applied.
   
   I am looking forward to Ramnivas Laddad's next book!



4. I loved this book, first of all the introduction is the most interesting presentation of AOP that I ever read.
   
   The other chapters are very good too since based on use-cases very easy to reproduce on projects...
   
   A book to have is you want to learn abour AOP (even if not interested by AspectJ per se...)



5. This book is an excellent resource for learning AspectJ. It is perfectly organized to take you from beginner, novice, to expert as you move through each of the chapters, just as you might expect if you were taking a class in AspectJ.
   
   The author's presentation of the material is straightforward and easy to follow, and his examples are not too involved that you lose track of what's going on. Furthermore, the author has an excellent grasp of the language and is really able to show off the power AspectJ has to offer.
   
   What I really appreciate about the book is that he focuses not just on coding, but also on design; I'm a software engineer and am very pleased that the author discusses an aspect as something to be used elegantly, as part of a well-designed system, rather than just another tool that can be abused. He even discusses several new design patterns that AspectJ makes possible.
   
   I truly recommend this book!

3 comments about Pro .NET 2.0 Extreme Programming (Expert's Voice).

1. Practical to the point book on agile software process.. Very nicely written, great examples. It covers the tools like NUnit, NAnt, CruiseControl etc + the whole extreme process - like user interactions / building user stories - building protypes - the design phase, implimentation phase and the testing and delivery, everything in a very interesting and light weight manner. So much interesting that I went through on the week end and never get lost. Authors, Greg Pearman and James Goodwill, did a great job in explaining this extremely mis-understood process. Most people that i know just take it a Unit-testing or a pair-programming thing.. thats all.. when you read this book you'll understand that there is lot more than these important issues especially the customer's needs. Great book a must have for every developer/team-lead even if you are not following this process. Cheers :) Shams



2. I picked up several copies of this book for my developer group to jump-start our progress towards test-driven development and agile programming.
   
   It's a very good introduction to Extreme Programming practices and the use of some of the tools used thereby. If you have a .NET development environment, this book is one of the few that you can pick up that isn't terribly dated or otherwise useless.
   
   Good solid advice and walkthroughs. An easy read, helps develop the concepts.
   
   Some flaws:
   
   1. (In my opinion) the examples of creating user stories were idealized almost to the point of hilarity. I've never found a group of customers that were willing to work in the way described -- but treated as an idealization, its otherwise okay.
   
   2. The section on using NMock is out of date, since NMock2 is out and it has completely different functions and methods. Part of the trouble with describing tools -- goes out of date quickly.
   
   3. No real discussion of Team Foundation Server, which handles elements of NUnit and CruiseControl. Probably because TFS itself is so new, there are relatively few books about it at this time.
   
   However, I think these are minor (sometimes unavoidable) points that don't really detract from an otherwise solid presentation.
   
   I recommend this book if you want to bring XP to your .NET developers group.



3. chapters 1-4 = 5 stars
   chapters 5-8 = 2 stars (i really hate the idea of focusing on tools in an agile book, but i can see how NUnit supports testing, NMock supports open/close design and testing, Cruisecontrol supports continuous integration, and how NAnt helps with continuous integration and automation of building/tests... etc etc. Basically if the author focused more on why we use those tools in xp as opposed to how to use the tools i'd be more happy with the presentation of them.)
   chapters 9-15 = 4 stars (i really skimmed through most of this because it was a really slow paced plodding walk through test driven development that could have been easily summed up in one example user story or two... i felt it was just there to fill up pages. It was, however, very thorough and, for the highly unimaginative, it could be useful)

5 comments about Software Testing In The Real World: Improving The Process (ACM Press).

1. This is an excellent companion book into the world of software testing. What it does do is highlight analytical techniques in how to perform tests. I frown at some who gave this book bad reviews in that they didn't understand the precondition for this book:

   1) This book does NOT teach the aspects of how to manage software testing or implement the procedures necessary to do so. This is a more detailed way of looking at things.

   2) Buy a book that teaches you how to implement the procedures and deal with all aspects of the organization in making sure these procedures are scoped out. Then, use the techniques in this book to implement the procedures.

   I find it extremely funny that the bad reviewers didn't see this - as they should know something about managing projects and communicating with users/management/programmers in a software test environment.




2. The title of this excellent book is appropriate with respect to real world issues are addressed. It's unfortunate that the real world rarely reflects what's in this book, but that is offset by the good fortune that you can establish and manage a mature, effective test organization by following the well thought out advice that the author provides. Since other reviewers have highlighted many of this book's key strengths I am going to touch upon what I like most and why.

   First, the author doesn't confine himself to testing in a vacuum - he gives a framework that recognizes the dependencies between and among other software engineering processes, such as configuration management, issue management and how testing fits within the development life cycle.

   Second, the underlying themes are risk management, cost containment and metrics.

   Chapters that I especially like are 1, the six essentials of software testing (in many respects this is the heart of the book and everything else is commentary), 5, critical choices: what, when and how to test (these are the eternal questions of software testing - the answers given are on the mark), and 10, testing tasks, deliverables and chronology (a deliverables-based approach is the only viable way to plan and estimate realistically in my opinion).

   While the above are my personal favorites, that does not diminish the value of the rest of the book. They merely reflect parts of this book that most influenced me. I cannot recommend this book highly enough - it's realistic, covers all of the important issues, and if you're like me you'll find yourself reaching for it when you have an issue to resolve or want to borrow a best practice.




3. Simple. Practical. Readily available thought frameworks for software testing. I consider this book to be a fundamental building block in testing community; not because it is high-end clean-room software engineering, but because it makes sense to the general person trying to understand, improve and apply. As with any facet of evolving software, this book is nicely complimented by reading some of Cem Kaner's works, in particular Testing Computer Sofware .. as well as.. look at James Whittaker's books and moving on from there by complimenting it with Glenford Myers historical work on testing .. but if you're simply looking for a clue .. start here and move to Kaner thereafter.
   
   Here is what I appreciated about Kit's book the most ... he diligently worked to talk to me where I am.
   
   This no non-sense approach makes a book that you can hand off to a green bean tester to introduce them to concepts, education, practices .. what works, what may not work, etc. You don't need to be a 10yr sw/test vet to understand and use his assertions and facts in your world. That, in my mind, makes the book purchase worth the cost.
   
   For example, discussing "..the quality of the test process determines the success of the test effort..". Seems obvious doesn't it? Now explain it to someone in such a way that they understand what behaviors they need to change/include to get from "nowhere" to "somewhere". Kit does it.
   
   Buy the book. When I recommend books to green bean testers, or testers with experience but no industry exposure, this is one of books I put on the "must purchase" list for them.



4. I manage a large development group for a Fortune 100 company; this group includes hundreds of testers. This is the first, and only, book I found that outlines the basic, core principles of software testing as they should be applied in a fast moving, ever-changing environment such as ours. I've made this book mandatory for every one of our testers and every development and test manager in my organization.



5. This book is an easy read, and gives the uninitiated like myself a good understanding of the basics behind softrware testing. Each chapter is short, well written, and to the point.
   
   As a subject matter expert on a software team developing a specific application, I found that this book gave me the background and information that I needed to have discussions with the testing team as they developed test cases for the functional verification of the application.

1 comments about Game Level Design (Game Development Series).

1. This book offers a solid foundation for the planning stages and a good overview of the implementation stages of level design. Good for those who are looking for general strategies for level creation and wanting to get up to speed on terminology/workflow for this type of work. It's all fairly theoretical with only one chapter on actual nuts and bolts level design, where you make a single room in the Unreal editor. If you're wanting something covering more specifics for a given level editor (like 'how do you create water?' or 'how do you make displacements') you should probably look for something more in a technical bible or a video tutorial series for the tool in question.

4 comments about Windows Home Server Users Guide (Expert's Voice).

1. Chances are, if you are reading about this book you have heard about Windows Home Server from Microsoft. Perhaps you are a computer enthusiast who wants to "roll their own" solution using the OEM version of the software (Microsoft Windows Home Server OEM); or maybe you are looking into a pre-packaged hardware solution like the offers from HP (HP EX470 MediaSmart Home Server (AMD Live/ 64 Bit Sempron Processor, 500 GB Hard Drive)); or maybe you just want to read more about what Windows Home Server (WHS) is and see if it meets your needs. Whatever level you are at, "Windows Home Server User's Guide" will help you learn more about WHS, guide you through what it can do and hopefully help you with your decision on what to buy, or help you decide if WHS is for you.
   
   There are a number of books that are coming onto the market about WHS. Many of them are large techical books that can drown the non-geek user with information that goes into too much detail about what goes on behind-the-scenes. Many of the books assume you are using the OEM software and building your own system. Instead of helping the user learn more about WHS, they confuse them with meaningless jargon and technical details -- precisely what Windows Home Server was meant not to do.
   
   Luckily, in this book the author has done a good job of keeping the book on a level that can be understood by all. He doesn't assume that you are using one solution or the other, but rather walks you through what WHS is and how it can help you regardless of the solution you end up using.
   
   Each chapter walks you through features of WHS and how it can help connect your digital home and family, and shows you how to get the most out of it. Throughout the chapters the author has put in side notes that give you alternative ways of doing tasks, suggesting where to go for more information or warning you about potential risks. The chapters themselves are concise and full of illustrations and actual screen shots to help you understand what steps need to be taken. In short, this is the manual Microsoft should have included with the software!
   
   I particularly enjoyed how the author covered more "geek" features of the product by talking briefly about them (such as the API -- or Application Programming Interface) but then instead of devoting pages on pages of text to something that both changes frequently and is too much information for the average WHS user simply points you to resources where you can find out more about it if the subject interests you. In this way the author stays true to the audience without trying to make this a "catch all" type book.
   
   In short, if you are getting ready to purchase Windows Home Server or are deciding on if this is a solution for you, I would highly recommend you pick up a copy of this book and read it. It will help you make a more informed buying decision and double as a great getting started guide to getting Windows Home Server setup and running in your house.



2. First of all, I would like to say I'm a big fan of most books published by Apress. I find the majority of them through on their given topic, and well written.
   "Windows Home Server Users Guide" is the first book from this publisher I've gotten where I feel like they let a book get past their editors that is nothing more than a fluff piece attempting to cash in on a new technology.
   This book does nothing more than to painstakingly itemize each and every tab and dialog that you will ever see in an attempt to bulk up a book that really tells you nothing. I found no added insight from this no-meat itemization of each field presented. Anybody that had what it takes to get their home server running could have written this book.
   
   Let's look at an example of where the writer attempt to expand on interpreting the log file if you have an error... this is taken directly from the book:
   "You will notice a series of error codes in the log file; for example, 0x8007000e. If the information
   contained in the installation log file is not very helpful, you might try doing a search on the Internet for
   that error code, or contacting Microsoft Product Support and telling them the error code and asking for
   some assistance."
   
   This is a common sample of the useless type of "extra information" that you can expect to get from this book. The rest of the text is nothing more than lots of pictures of each and every screen and dialog you will ever see, accompanied by write-ups similar to the one I have given. In fact, to find this example, all I did was randomly pick a page out of the book to prove this point. I did not look for a particularly bad example, but just the first example that I opened to.
   
   In summary, Apress is a publisher that I have grown to trust, but after this piece of swill, I will be focusing a more critical eye on them before I purchase sight-unseen again.



3. For the life of me, I don't understand the harsh review this book got. The main critique seems to be that the book isn't meaty enough. Having used it to get me through my first WHS install and two subsequent ones, I find that charge a bit, well, unfair.
   
   The book essentially goes through each Tab in the Windows Home Server console - that much I agree with in the other review. But I found that every single feature I was interested in was covered in more than enough detail to get me through it but never got longwinded or boring. It's precisely the concise nature of the book that makes it so useful. It's light and small, you can easily store it near the computer and you can *find whatever you want quickly* in it.
   
   The truth is, WHS is pretty straightforward and there's not a whole lot to it. What you see on the tabs if pretty much what's there other than Add-ins and the System Settings. The only really tricky task that I found was getting Remote Access to work and this book got me through it with flying colors. In fact, the same goes for every other task. Instaed of installing it and trying to figure it out later, I used this book as I went along and had no problems. The *only* thing I found tricky other than configuring remote access (and it's not the WHS side that's the problem, it's the router) was syncing user accounts on WHS with other accounts to machines I hooked up with Connector.
   
   Although I would have been pleasantly surprised to find a little more on the WHS SDK, every single important topic is covered and covered well. The author does a phenomenal job of getting to the point, telling you what you need to know and not confusing it with stuff you won't care about.
   
   Overall, it's an excellent book and the perfect WHS companion.



4. Well as I have said there are currently 6 Windows Home Server (WHS) books on the market and i'v read them all (yikes). So is the User's Guide from author Andrew Edney any good?
   Yes, Yes and Yes. What Andrew has managed to do is write a complete guide of getting the most out of your Windows Home Server. Whether you are a beginner or a seasoned pro there is something for you within the books 300+ pages.
   Starting with what WHS is (just in case you didn't know), Andrew then takes us in detail, through the features of the product including how to install and most importantly the steps you should follow once installation has finished.
   Andrew also includes a network primer and details on how to build your own Windows home Server as well.
   Thoroughly recommended and defiantly one of the best WHS books currently on the market.

No comments about Software Security Engineering: A Guide for Project Managers (The SEI Series in Software Engineering).

5 comments about USB Complete: Everything You Need to Develop Custom USB Peripherals.

1. This book is an excellent guide to start with usb hardware, if you want to know where the head and feet of usb are, read this book.



2. This is probably a harware designer's book. If you ever plan on designing or undestanding USB hardware, this is definitely (no matter what cost), the book for you. Jan Axelson has written for many EE mags, and knows what she is talking about. The book may be getting dated, as a few of the chips she descibes are obsolete, but who cares - the data is relevant. Very well done, and very readable.



3. This is very good introductory book on USB for embedded devices. It provides a good overview including a brief comparison of USB with other devices. Admittedly the term complete is a bit of an overstatement; if your going to program own Window's drivers you're going to need a lot more information than is provided here. However, for small-run embedded developers and hobbyist this book is ideal. It is up-to-date and provides a the information you need to consider before jumping into USB development. One of the other reviewers complained that this book spends a lot of time on third-party products. However, for those of us that are grudgingly porting hardware from RS232 to USB this very helpful and very important. Yes all of this information is on the web; but much of it is misleading. For example; a lot of people start with and HID (human interface device) as it does not require a special Windows driver. The online documentation for our developement system gave the data transfer rate as 1.5Mega baud. However, reading this book you find that your likely only to get a fraction of this speed and the guaranteed transfer rate is only 800 bytes per second which is positively glacial.
   
   The USB interface is very complex. One of the major issues is that anything you develop will likely require drivers for both the PC and the device. In choosing a vendor is probably more dependent on the quality of the drivers and the quality of the documentation of the drivers than on the hardware itself.



4. This book is highly recommended considering it's depth and range of content. It offers lots of practical information and is easy to read. The website that supports this book is also very helpful. If you are interested in USB, this is the first book to read.



5. Anyone who is new to USB interface and products should read this book first. I bought an USB evaluation board to get an understanding of USB.
   When it would not interface with our product the way I thought, I was very disappointed. After reading this book, I realized there are major differences with the USB microprocessors. I then was able to purchase AN USB evaluation board with an appropriate microprocessor that would interface with our equipment.