Computers Books

This book thoroughly discuss the steps in using auto cad 2D and an opener in 3D autocad drafting. It uses a simple terms that anybody even not engineers can understand. Must buy for a beginner to intermediate autocad users.

The delivery from amazon really surprised me as the book arrives ahead of thier given arrival time. It arrives in two days only, supposedly shall arrive after 3-5 days. another 5 star rating for amazon's delivery system!

Easy to follow, Lots of excercises to practice with and explanation when you screw things up (beyond repair, sometimes.
A must read if you want to go to "AutoCAD University"?

AUTOCAD 2006 AND AUTOCAD LT 2006: NO EXPERIENCE REQUIRED is a fine, basic introduction to a powerful program which once commanded the attention only of professionals. Any seeking to utilize the CAD software should have this manual in hand: it provides a set of tutorials which are sequentially arranged for step-by-step study - but it also can be used as an at-a-glance reference sourcebook for solving specific problems. From understanding coordinate systems and drawing routines to working with fills, text, external references and more, AutoCAD's powerful tools and drawing features are all detailed in depth.

Diane C. Donovan
California Bookwatch

I work for a survey company. I have never been to college and I am a self-taught AutoCAD user. I learned AutoCAD '02 with this book. Now I train guys and we buy this book for guys that have backgrounds with Microstation and are transitioning to AutoCAD.

Fantastic book for the experienced or the beginner. Easy to understand. Highly recommmend for those just starting out.

Despite its title this book is an easy and entertaining read for a broad audience. While specifically written from the perspective of management of software projects, the book actually addresses management at large. It makes a concise case showing how dangerous and detrimental it is (to the successful outcome of large scale (software) projects that is, defined by the author as a "quality product on time and on budget") to separate technical leadership/management from personnel leadership/management, as so often mandated by many organizations. The "manager-architect," as termed by the author in his book, is key to success. Consequently not everybody can be up for this task, and only few who dare to try will succeed at it, as evidenced by the disconcerting fact that many "top level managers" manage nothing but major budgetary overruns (be they hidden or not), for which they are "held accountable" by society by being hailed as "America's Best Leaders." This book puts an end to such phoniness and provides especially the inexperienced/naive reader with a skill set to reveal/uncover such mismanagement and the individuals responsible.

The book is a true eye opener for aspiring and "want-to-be" managers alike. Also, having posters on "true leadership" pinned to the office wall does not magically inhale the ability of leadership into the office occupant. Leadership is an ability rather than a skill as clarified by the author. It is just like playing an instrument: it only gets you so far if you do not have it in you and practice every day. Chapter 12 "The Impact of Leadership on Software Development" should be read by any manager (aspiring, "want-to-be", or acting alike), and in particular by those who confuse management with suddenly having power over people. Moreover, management does not and should not mean "tenure" along the lines of "now I have made it, now I can relax" or "now I am in power." Rather the "Old Fritz" (Friedrich II, Prussian King) statement, simple yet true, comes to mind: "I am the first servant of the country" ("Ich bin der erste Diener meines Staates"), and serves as a good guide.

The author puts forth an interesting concept for true autonomy founded on the philosophical considerations of the human mind, upon which the AI-(IF-THEN-ELSE)-community will most likely have to choke. In doing so, the author outlines nicely the profound difference between automation and autonomy, two terms, which are often confused, intermixed, or misunderstood, even by so-called experts in the field.

If management is done right, as exemplified/laid out in this book and practiced by its author in an exemplary fashion, managers would rather have to be pitied because of their huge added responsibility for their people/troops and the projects they manage/lead (in that order!). Special attention should be paid throughout the book and in particular throughout Chapter 12 to the "Machiavellian Prince," as this kind of "leader" unfortunately exists (and not in small numbers!), and, while striving only for personal power and gain, causes a lot of damage to otherwise noble causes.

The author of this book has deep insights and wisdom for any level of interface with computer science applications. You simply cannot go wrong for putting your weight down on patterns to follow from someone who has had success in the field. The techniques in this book go beyond basic head knowledge, into the live action of software development where the rubber meets the road. Only an experienced person can give these insights. I am very impressed with the advanced mapping, made simple. This book seems to be written for people who are looking to find answers to every day problems in a rapidly moving computer world, without fear.

Mr. deGyurky gives a great overview of his experience at JPL in organizing and developing large, complex, software systems, and delivering them on schedule, on cost. Mr. deGyurky demonstrated that the most important contribution to software management is that of leadership in life, carries over in software development also.

If you are thinking of becoming a manager of a software development project, you should check this book out, and You will be a step ahead of the game!

The author has given us a framework for conceptualizing, organizing and developing large, complex, software systems, and delivering them on schedule, on cost.

His approach to software development emphasizes two basic ideas. Unique is his application to the development process of the cognitive philosophies of the great Nineteenth Century German cognitive philosophers, principally Schopenhauer, Kant and Hegel, which De Gyurky has studied for years (- in the original Nineteenth Century High German). De Gurky also emphasizes to an extraordinary degree the active role of personal leadership required of the successful software development manager.

Far from being a purely theoretical work, the book is richly illustrated with pungent examples from De Gyurky's near-incredibly varied experience both in the US military as a Special Forces officer commanding a detachment of Montaignards in the mountains of Vietnam, as an action officer at NATO Headquarters, and as the civilian developer of very large military flight-schedule management systems as well as spacecraft software command and control systems.

All the examples are exquisitely pertinent to the software development process. But in addition, four detailed programmatic examples are presented, together with comments, figures and schedules. The author's application of the principles he developed is wholly consistent and unfailingly pertinent, if sometimes challenging, due to the likely unfamiliarity on the part of the typical software engineering reader with the application of the philosophical concepts.

In fact, the single characteristic of the book which may challenge the typical software developer is the accessibility of some of the concepts. Some of the most powerful concepts discussed, e.g., the dialectical process by which an ill-formed idea becomes an object that reflects the meeting of the minds of the design team, are likely to be unfamiliar. However this process has profound implications for the organization of the design team, its management, team-member responsibilities, and on and on. It might have been helpful if the author had expanded on these key concepts, perhaps in context closer to their original use. It would be demanding on the reader, but probably no more so than parts of the book itself.

This unique contribution is recommended to software developers interested in on-time, on-cost development of large software systems, and willing to invest in the intellectual effort required to understand the author's unique contribution. They will be well rewarded.

I have read many books on systems and software development and management principles over the years. The ones that most influenced me were: "More Reliable Software Through Composite Design" by Glen Meyers; "Up the Organization" by Robert Townsend; and "Reengineering the Corporation" by Michael Hammer and James Champy. And of course no system developer's library would be complete without "Managing the Software Process" and other books by Watts Humphry, a giant in our industry. Mr. Szabolcs Michael deGyurky's book will occupy a place along side these on my bookshelf.

In this book, Mr. deGyurky has provided a completely different and refreshing, but no less important, viewpoint on systems development. As different as all the above mentioned books are, the one theme common to all of them is their focus on the "real" problem by differentiating between the truly important and the seemingly important - commonly referred to as separating the wheat from the chaff..

"The Cognitive Dynamics of Computer Science" focuses on strength of character as being indispensable to successful completion of complex systems development projects, which not only satisfy the "real" requirements, but ensure the system is delivered within an agreed to budget and schedule. This book draws on the philosophy of such estimable historical figures as Kant, Hegel and Schopenhauer, among others, in defining the behavioral characteristics of successful leaders and managers. Personal experiences in real world projects by Jet Propulsion Laboratory (JPL) provide a substantive backdrop for Mr. deGyurky's approach to managing systems development.

It is impossible to adequately relay the impact of such a book in so short a review, but I do come away with some points which derive more meaning because of my own experience: 1) Design from the user in, but develop from the inside out, in layers, 2) Don't implement until you have an initial design documented and understood by the development team - expect that to change, 3) Manage change through the Project Implementation Plan (PIP), which is the Project Manager's equivalent to the Software Development Folder, 4) Don't hire staff until you have their tasks well defined (control burn rate and you have controlled your budget), 5) Make sure you understand exactly what your customer wants through constant customer involvement, 6) make your customer's goal, your goal, then incentivize the entire development team to focus on that goal as the highest priority, 7) There shall be no implementation without documented, repeatable process and standards, which should be tailored to the individual project, but at no time should process and standards replace common sense in a dynamically changing development environment, 8) Employ tools and ensure the team is involved in their selection, 9) Ensure the development team is trained in methodology, process, standards, tools and system requirements, and 10) the manager should place the needs of his customer and his team ahead of his personal goals.

All of this is done in concert with the philosophical teachings of our great philosophers, who would encourage strict honesty and ethics in dealing with our customer, subordinates, colleagues, company management, even if it means being fired. Of course, one does not fit all the meaning of a 300-page book into such a short review, and one could easily list another 10 or more points of interest.

I agree with almost everything in this excellent book, but may differ on the role played by Computer Aided Software Engineering (CASE) and Computer Aided Design (CAD) in systems development. Since CASE tools became mature enough to use effectively, I personally selected my tools, then built my process and standards around them. This includes the way I modify process and standards (including DoD) to conform to streamlining development and associated documentation. The CASE tool, when used with discipline can ensure that interface errors are avoided during the design process, as provided through automatic leveling and validation as the system design progresses. Fixed price contracts caused me to gravitate to using the latest tools available and build around them each time.

I am certain that Autonomous Cognitive systems are in our future, but not without application of increasingly sophisticated CASE tools and compilers (Autonomous Cognitive Compilers), which can parse complex combinations of Boolean expressions with many operations per expression to simulate the human thought system in making decisions. Neither can these systems be built without addressing the transducers (sensors), which would connect to and provide stimuli to be interpreted and processed by any autonomous system as the 5 senses (sight, hearing, touch, smell and taste). I look forward to Mr. deGuyrky's next book, which may address this highly complex problem.

I would only close this review with one last comment, directed to JPL. Mr. deGyurky and his team were on the right track with Ada. It is unfortunate that JPL didn't adopt this very highly typed and disciplined high order language as their standard development language. I believe it would have saved more than one failed project. Based on my 40 plus years of developing computer systems, I would humbly suggest that JPL require mandatory use of Ada in all "Class A" development projects.

I have to say that this is a true classic. It gives a very nice treatment of what is NP-completeness in a fashion that really defends the topic well. It gives nice illustrations to show different situations and how to deal with it. But after the first couple of chapters it does get a little out there with the proofs it does. It is still approachable, but it assumes that the reader is already familiar with the basics of combinatorial complexity, especially in reductions. I would only recommend this book to readers who has gone through such books as Introduction to Algorithms by Cormen et al. or Combinatorial Complexity by Papadimitriou and Steiglitz. Those two books are more for beginners and this book should be one to help anyone interested in NP-complete problems to get more practice and depth understanding. Overall a great book for anyone interested in the topic. The grand challenge is to reduce everything to at least something within the 150 problems listed on your own.

The book is excellent in explaining NP-completeness problem. Take it as a reference if you would like to do research in this field.

This is a rare example of a textbook where the authors actually go to the trouble of considering the fact that the intended reader is a non-expert. Published in 1979 and still the best.

The book arrived in time, in good condition, and adequate packing.

This is among the most eloquently written books that I have ever read in my life. Highly recommended.

As a software developer, you know that one of the critical period in a project is when you try to make integrate your code in the overall application and push it towards the final user. It is sometimes a long process that you would like to accelerate so that you could obtain a quicker feedback on the quality of your code. This book written by Paul Duvall, with Steve Matyas and Andrew Glover, will help you improve the way you build and deliver software.

After a initial presentation of the continuous integration (CI) concepts and objectives, the content of the book goes far beyond the simple "continuous build" aspect to cover all disciplines concerned by CI: risk management, configuration management, database evolution, software testing, inspections, deployment. It is clear that CI is just not installing a suite of tools, but is mainly changing software development practices and process. Each chapter is well structured with practical examples related to real life situations. The book reach also nicely the objective of maintaining a balance between a somewhat tools- and language-neutral position, but still giving enough practical advice so that you could quickly adapt the advice to your own software development environment. Final appendixes give valuable information on CI resources and evaluating available CI tools.

Finally, you can get more and updated information on continuous integration and download book's chapter two from the Web site associated to the book: http://www.integratebutton.com

Any software developer who has spent days in 'integration hell' handling a complexity of software components will appreciate the invaluable information in CONTINUOUS INTEGRATION: IMPROVING SOFTWARE QUALITY AND REDUCING RISK. From the initial concept of CI and its practices to over forty CI-related practices from database integration to development, this book covers the entire cycle of CI development and surveys all kinds of events, repetitive processes, and more. An outstanding guide any serious software development library needs.

This book is a good one - it has lots of well stated reasons for doing a continuous integration system of some sort, including all sorts of little conversational snippets that help make the point. For example, "Jim: hey, the test server isn't working. Joe: Ah yes... I forgot to 'svn add' one of my source files." Doh!

He suggests using one of those ambient orb gizmos to provide visual feedback on failed builds. That's probably a better idea than a sound alert - I found that having one of those go off every once in a while was just annoying. You can cut an email to everyone when a build fails, although that risks folks just routing them to a folder and letting them stack up.

I was happy to see that the section on static analysis included lots of suggestions for using PMD and CPD. CPD, especially, is a handy tool; the ability to find duplicated code across a large codebase is very nice.

One of the hard things about a book on CI is that CI touches so many different parts of a system - the database, scripting, code, tests, code analysis, etc. It's not the sort of book that lends itself to one big example; instead, you have to have a bunch of little config files and scripts and examples to help a person get rolling down the CI road. I think they did a nice job here of having a good mix of theory and practical code samples.

So anyhow, I think this book is a good 'un. Go get it!

As an aside, I was a technical reviewer for this book, so there's probably some bias there. But not too much!

As Martin Fowler says in his foreword to this book, all of this information is available on the internet. However, that should by no means demean the value of this book. This is an extremely readable and well-organized presentation of this important development practice. Often the organization and comprehensive analytical thought are themselves important contributions to a given topic, and that is what Duvall, et al deliver here. Highly recommended.

This book is an excellent overview of why Continuous Integration is important and about more than just compiling frequently. The book helps you to understand why to do CI, what you can do beyond building, and how to do it. In addition to general principles, the book points you to some excellent tools and resources. This book is an excellent companion to Software Configuration Management Patterns: Effective Teamwork, Practical Integration; it provides teriffic information that support the build patterns in that book. You might already know some of the information in this book, but it is worth buying if you need to encourge CI in your organization for the clear discussion of why CI matters and the for the detailed advice on how to implement it.

The simplicity, yet thoroughness, which he uses to explain one of the more difficult topics in engineering and mathematics shows that Dr. Hershey is a true expert in the field. I highly recomend this book for both the novice and the advanced reader.

Cryptography Demystified is a great intro guide to cryptography, well worth its price.

If you can make sense of this then you'll be able to make sense of the rest of the book (From Module 4):

Prob[p(t)=1lc(t)={Prob[c(t)=1lp(t)=1]Prob[p(t)=1]}/{Prob[c(t)=1]}
Now,
Prob[c(t)=1lp(t)=1]=Prob[k(t)=0]
and
Prob[c(t)=1]=Prob[p(t)=1]Prob[k(t)=0]+Prob[p(t)=0]Prob[k(t)=1]
therefore,
Prob[p(t)=1lc(t)=1]={prob[k(t)=0]Prob[p(t)=1]}/{Prob[p(t)=1]Prob[k(t)=0}+Prob[p(t)=0]Prob[k(t)=1]}

This book is slanted towards more theory and math than others that deal in practicality, for instance "Cryptography for Dummies". But if you have a solid foundation in mathematics and have the temporal ability to "quantinize" then this is a fantastic book. I would speculate this book is meant for graduate comp. sci/eng coursework as it is broken down into 35 Modules with problem solving exercises at the end of each. At any rate, good luck!

This book was used in a course I took taught by the author, Dr. John Hershey. I have read and own several books in this category, am working to obtain two advanced degrees in the field of computer security, and feel that I have enough information to write an objective review. It is an excellent introduction book to the general area of cryptography, but suffers from several shortcomings.

If you do not know much about what cryptography and encryption are, this book should provide a decent introduction. The book provides the mathematical concepts needed to understand the chapters, but I felt it did not cover enough detail or provide enough examples to let me feel I had a solid understanding of everything.

There are three aspects to cryptography: authentication, integrity, and verification. This book only discusses integrity issues, i.e. encryption. DES, RSA, and Diffie-Hellman are discussed, but a detailed covering of AES is noticibly absent. It covers integrity rather well, breaking down the different methods of using block encryption into separate chapters. In other words, DES operation in electronic codebook, output feedback, and cipher feedback modes are three different chapters. This is something that isn't usually done and is a rather nice touch. It makes it much easier to learn the advantages and disadvantages for each mode of operation.

In terms of total mathematical theory, Hershey's book does not contain much theory. If you want theory, I recommend you find William Stallings book titled "Cryptography and Network Security: Principles and Practice." Also, Hershey's book does not contain code to let you start programming a security system. If you want applications, I recommend you find Bruce Schneier's book titled "Applied Cryptography: Protocols, Algorithms, and Source Code in C." Those books are for advanced readers, however, and may be difficult to understand if you don't know the area.

Overall, it is a good read. I recommend it more for IT people than computer scientists or engineers simply because it touches upon the topic, instead of being very detailed. Look at the editorial review section criteria for who should read the book, it is right for the most part.

If you are looking to expand your mind, think about learning Cryptography. It is an excellent discipline to help you think in new ways. If you decide you want to learn Cryptography, this is the book for you. The book is written in modules, making it easy to digest. The book is equally suitable for a formal classroom or self-study environment. Using the book for self study is enhanced by the modular format, superb clarity of the teaching, the well-explained answers to the problems, and the appropriately injected humor. People that need to learn Cryptography will undoubtedly have this book on their shelf, whether they are an expert or beginner. I would like to speak to the people that don't need to learn Cryptography - this book is for you too, as you will enjoy learning the thought processes of Cryptography that will enhance your creativity in any field. This book is a gift.

Ron Penton, Data Structures for Game Programmers (Premier, 2003)

I don't normally get all googly-moogly over programming books. In fact, I just took a quick look back at my reading log since 1999, and a select few have gotten four stars, but nothing above that. But I picked up Penton's nine-hundred-page tome on Thursday and I finished it on Sunday. Nine hundred pages in four days. I've only been keeping track of page counts over the past year, but the books I've read that have come closest, page-wise, have been Robin Hobb's lovely novels, three of which I read earlier this year hovered around eight hundred pages. I read the shortest of them in eight days. And I love Robin Hobb.

Data Structures for Game Programmers is a wonderful book in no small part because Ron Penton was still an undergrad while writing it. Which is, of course, also the book's main problem, because someone like me who last saw ivy-covered halls well over a decade ago is likely to be sick with envy that some little greenhorn has already found his way into the world of professional computer-book publishing (and by "professional" here I don't mean "published by recognizable press," I mean "the kid's already published three books in three years, and they're ALL monstrous tomes, when does he have time to program?"). But let's face it, you expect something different when you read a book by a young writer, be it the hot new novelist or the new kid on the programming block. And Penton delivers it; Data Structures for Game Programmers is, if you're a programmer, the most readable computer book you've ever come across. Penton seems to have a healthy disrespect for textbooks, which he alludes to a few times in the course of the book, and it shows in his writing; he wants to write something that will teach you more than a textbook by being more accessible. And in this goal, he succeeds. Brilliantly. I learned more about C templates from reading this book than I have in any other three books devoted to nothing but templates, and here they're just referred to a few times in passing. How is this possible? Because Penton explains things in language far easier to understand than that of most programming books; simply put, he hasn't yet been so overwhelmed by jargon that he can't see when he's written something the layperson might not be able to understand, which is a common ailment among programming authors.

Also, there's been some minor grumbling from some critics about the book's insistence on reinventing the wheel. Of course it does. That's how you learn to program-- you bang away at it, doing something that's already been done, until you figure out why it's done that way. There may be five or six people on the planet who can read it in a textbook and immediately figure out why it's the case (and, one assumes, they are the same people as those critics), but the rest of us are much happier seeing it this way.

If any computer book publishers happen to be reading this, you, especially, should be reading Data Structures for Game Programmers. See what it's like. Try to get the rest of your authors to emulate it. You'll have much happier customers that way.

This is one of the handful of books I've read since getting a library card again (a total, in fact, of four since 2003) that, after returning it to the library, went back on my Amazon wish list, because I want a copy for myself.

i wanted a book to brush up on some data structures since i've been out of programming for a few months. plus, most of my learning of these has been self taught and from the internet where there is limited (good) writings on more complex subjects such as programming. so i wanted to have a fresh perspective. not only does the book contain very useful details in many areas and to the point information (gets to the first data structure by page 14!) but the author somehow makes this stuff fun to read.

the author doesn't go hugely in to depth in some areas but that's pretty much what i wanted since i am already familiar with how to use most of the stuff. very good book and i'd highly recommend it. hope this author continues with more books!

This book actually teaches Data Structures!! Data Structures are the essence of programming. Ron manages to present all the basic Data Structures and the most famous algorithms in a clean and gentle way.

Many many thanks to Ron Penton for his help! Ron Penton really knows how to write a book! His way of writing shows that he knows the subject perfectly and presents it in a way that anyone understands what he is talking about. No matter how hard the topic is! By the way, Ron Penton has a great sense of humour!

If I could I would give one more star for the GREAT job he did with the CD. Although I intended initially to learn Data Structures, I also learned SDL. Perfect combination for someone who wants to start writing games!

A pre-requisite for any book on Data Stuctures is that the person should be comfortable with the syntax and semantics of programming in a high level language such as C++ or Java. Hence this book assumes that you are comfortable with C++ and OOP. There is no such thing as Data Structures for Absolute Beginners. So discard the review with 2 stars. Overall this is an excellent and interesting book on Data Structures.

Bottom line is this, you can find the information presented in DS4GP in any other good book on data structures but what sets this book apart is the presentation, organization, practical content and the writing style of the author.

It's definetly not for beginners or for a person looking for a very detailed book on data structures that covers AVL trees and red-black trees. But for the other 99% its a must buy.

i wanted a book to brush up on some data structures since i've been out of programming for a few months. plus, most of my learning of these has been self taught and from the internet where there is limited (good) writings on more complex subjects such as programming. so i wanted to have a fresh perspective. not only does the book contain very useful details in many areas and to the point information (gets to the first data structure by page 14!) but the author somehow makes this stuff fun to read.
the author doesn't go hugely in to depth in some areas but that's pretty much what i wanted since i am already familiar with how to use most of the stuff. very good book and i'd highly recommend it. hope this author continues with more books!

I love this book. It should be required reading for all undergraduate and graduate business students. I'll be looking for Windham's next book.

I must congratulate Ms. Windham on her excellent book "Dead Ahead". I think I must have read it more than three times by now. I am a consultant and my company is involved in web design and development. On many of my assignments, I relied on this book as a guide and many of her ideas have worked very well with my clients.

Our company provides e-commerce and web presence solutions. We use "Dead Ahead: The Web Dilemma and the New Rules of Business" by Laurie Windham extensively to help us provide effective solutions for our clients.

Dead Ahead covers the 'new rules' of web-based commerce, from using existing businesses and strategies to succeed to establishing recognition and associations via the internet. Important chapters on investing in the right technology and conducting e-business make for important insights on the rules and atmosphere of the web.

This was used as a text book in my e-business MBA class and would recommend it to others outside of class. It covered a lot of issues relevant to the topic. I enjoy reading books like this that are up-to-date in a dynamic industry.

My husband bought this for me when he bought me Photoshop Elements, and it was immensely helpful! I am now very comfortable in Photoshop, thanks to the easy to follow instructions and visuals.

The volume's strong point is its voluminous visual to illustrate every phase of digital photography from equipment to printing paper. It also bridges the gap from optical to digital photography. Technical in presentation ... for the experienced phohtographer ...

A profusely illustrated with more than 1500 full-color photographs, step-by-step 'how to' guide for taking great photographs and then digitally enhancing them using Photoshop, "Digital Photograph" by Michael Wright is very highly recommended both for its comprehensiveness and for being so 'user friendly' in its organization and presentation. Covering Photoshop essentials in general, including Photoshop 7 and Photoshop CS in particular, "Digital Photography" addresses simple and complex retouching techniques, removing 'red eye' from images, cloning, hand tinting, restoring old photographs, photo montages, digital painting, adding text to images, special effects, storing images, creating photo essays, printing, file size, composition, color theory, bracketing, lighting, backgrounding, and so much more. "Digital Photograph" is a single volume instructional guide that is strongly recommended for anyone aspiring to enhance their photography through Photoshop technology.

More pictures, less words, better understanding! This book truly is a step-by-step visual guide for taking pictures, and then whipping them into shape in Photoshop.

This book is not about about how to take better digital photos. It's a book that gives step by step instructions on how to do numerous photo editing. If you're not experienced in PhotoShop, then I highly recommend this book. For a novice, it might be a good refresher for you.

One of the things I love about this book is it actually does give step-by-step visuals on the how tos. It shows you what the photoshop box will look like, tells you were to find the tools you need, etc.

If that's what you're looking for, then this book is ideal for you. As I said, if you're a novice, it's a nice refresher or quick reference book.

I was mainly interested in the MES implementation part and I found those chapters quite inspiring. We are usually lead by "common practices" which form our experience and we'll use them throughout our work. But formalizing and being able to communicate a technology is always an issue (unless you're going to di it all by yourself).
Excellent.

"Domain Specific..." is another excellent book from the "Fraemwork collection". It is a set comprehensive reference books as well as a authoritative textbooks by experts in this growing research field.

The description of practical experiences as well as more conceptual descriptions, are usefull to understand the complexity of achieving high levels of software reusability.

Managers and academics, will find a lot of material to help them decide if this is the way to go. Our research group in Web Engineering at the University of Sydney (weg.ee.usyd.edu.au) will us it extensively to improve our development practices.

An almost indispensable 3-volume reading to understand the success of framework technologies in today's software systems. The books include most of the top
articles on the subject, providing a thorough insight in both design and implementation issues regarding frameworks, also complemented with practical experience
about framework usage. Although the work is mainly concentrated on technical aspects, the articles are comprehensible enough to be taken as reference material by
a broad community, for example, software engineers, programmers, or technology managers. The books are useful for anybody planning to include
framework-based techniques in software development processes or planning to improve current object-oriented practices. It is also an excellent source for graduate
courses.

Volume 1 lays the fundamental concepts supporting object-oriented frameworks, and describes the problems and challenges that this
technology raises in software development. The book covers topics such as domain analysis, development concepts and approaches,
documentation, and management, among others. Of course, the compilation of articles makes some parts little redundant, but this is a minor detail compared with the
fruitful contributions made by the book. In particular, the articles on reusing hooks, hot-spot-driven development, composing modeling frameworks in Catalysis, and
composition problems, causes and solutions, are a sample of the outstanding level of this work. Each chapter adds at the end a number of related questions and
student projects aiming to reinforce concepts and promote further investigation. As a comment, novice readers should take the sections concerning hooks and
hot-spots carefully because these topics are presented in a slightly confusing way.

Volume 2 focuses on specific framework implementations, dealing with existing frameworks for different application domains, such as businesses, multi-agent
systems, languages and system software. In this book, the readers will find a level of detail much closer to specific implementations issues than in the previous
volume. Nonetheless, the writing style remains mostly clear and accessible for a quite broad audience. The case-studies and experience reports described by the
articles show an attractive industrial perspective of the framework approach, and more important, they go an step forward in the road of a more mature discipline for
software development. In addition, a
CD-Rom with concrete examples of these applications is included with the book.

Volume 3 completes this series with a number of domain-specific application frameworks developed by industry, showing how to apply the concepts and ideas of
the previous books in software products. In this line, it includes very interesting frameworks for manufacturing systems and distributed systems, among others. It also
goes through concrete software scenarios, illustrating the benefits of combining domain knowledge and object-orientation expertise. Although the level of the articles
is rather odd, the volume certainly provides the readers a realistic picture of the problems of building and adapting frameworks by learning from others' experience.
A CD-Rom is also included with this book.

Overall, these framework books collect the state-of-the-art on framework development, offering a comprehensive and
easy-to-understand guide for both academics and practitioners in the field. It is clear that framework technologies will not solve all the problems (perhaps they rise
more challenges than current approaches), however, taking advantage of the framework possibilities can make your development process more repeatable,
productive, and also less painful. The gains of this retrain are no doubt a good investment.

A great reference and compilation of timely material. For anyone interested in frameworks targeted to specific application domains, this book surveys a broad spectrum of example systems while providing detailed in depth information concerning the particular requirements and features necessary for each domain.

This book in conjunction with the books "Building Applicaton Frameworks: Object-Oriented Foundations of Framework Design" and "Implementing Application Frameworks: Object-Oriented Frameworks at Work" are a series of three books that constitute a complete and necessary guide for the design and implementation of application frameworks. They are based on multiple academic and industrial contributors experience building a wide range of domain-specific application framework. These books are very easy to read and understand and you can learn from them not only what a framework and an application framework are, but also how to apply this technology to real world domains, like manufacturing, health care, distributed computing, real-time systems, simulation environments, ...

First book, "Building Application Frameworks: Object-Oriented Foundations of Framework Design" introduces application frameworks, their benefits and problems. It addresses all the fundamental concepts behind OO application frameworks and provides guidelines for OO application framework development. It is organized in eight parts. Part one provides a complete overview of OO application framework technology describing what is an application framework, what are the problems and benefits of application frameworks and how to use, develop and evaluate an application framework. Part Two presents some historical application frameworks and discusses some general guidelines to increase the reusability of application frameworks. Part Three describes how to build a framework analysing a concrete domain. The rest of the book provides all the necessary information to completely build an application framework. It presents all the concepts managed in framework development, which are the different development approaches, how to test the resulting frameworks, the problems derived from integration and a question sometimes forgotten but very important, the framework documentation.

This book, "Domain-Specific Application Frameworks: Frameworks Experience by Industry" is focused in the experience of industrial and academic contributors in the development of OO application framework in different domains. Each chapter covers step by step the complete development of an application framework in manufacturing, distributed systems, real-time systems, telecommunication, multimedia, chemistry and data visualization domains. It includes the motivation developers founded to choose application framework technology, the problems they had to solve and the final solutions they developed.

Third book, "Implementing Application Frameworks: Object-Oriented Frameworks at Work", shows step by step how to implement application frameworks in different domains. It is organized in six parts covering examples about i) Business Frameworks with different examples in sales and administrative domains, ii) Artificial Intelligence, iii) Agent Application Frameworks, presenting interesting frameworks for speech recognition, neural networks and agents. iv) Specialized tool frameworks, v) Language Specific Frameworks, vi) System Application Frameworks, which present and analyse the application of OO frameworks in combination with other methodologies as component-oriented programming, language constructs or constraint programming and vi) Experiences in Application Frameworks. This last section is very useful because analyse the lessons learned using the application framework technology.

I bought this book quite a while ago and I absolutely the format. It's a great resource to just pick up and get great ideas, verify that you are on/off the right track and generally learn how to get to the next level with XML. Highly recommended

The flexibility of XML can often mean that there's a gap between using XML and using XML effectively. Elliotte Rusty Harold's book Effective XML - 50 Specific Ways to Improve Your XML (Addison Wesley) is an excellent way to move towards the latter condition.

Chapter List: Syntax; Structure; Semantics; Implementation; Recommended Reading; Index

There are obviously a large number of books that will teach you the semantics of writing and using XML. But just because you can create an XML file doesn't mean that you've done it well or effectively. Harold's book provides a bridge to being able to create XML files that will be usable in nearly all situations. The book starts out in the introduction with explanations of terms that are often confused (element vs. tag, text vs. character data vs. markup, etc.). Then there are four parts of the book that include a total of 50 tips that will improve the quality of your XML usage. Some tips are pretty basic, like "Include an XML Declaration". Others are more complex like "Verify Documents with XML Digital Signatures". But every one is practical and useful for making sure that your XML is widely useable by all potential applications.

Excellent bridge book to read after you've learned the basics of XML. This is a book that, when taken to heart and used, will cause your coworkers to thank you.

Effective XML is a collection of about 50 tips for working with XML. Although XML seems is simple and easy to use, it's also easy to get wrong. I've often scratched your head and wondered why things like XML Schema, for example, just doesn't feel right. But it wasn't until I read Effective XML that I understood what was really awkward with it.

Because the book is so diverse (an amazing feat considering the small page count), it is hard to single out any specific part as being a reason to read the book. The book doesn't just talk about schemas, the infoset, etc..., it digs down and really explains what is good and bad about the technologies and what the best ways to apply them are. All I can say is that I use XML day in and day out and have learned everything I know by trial an error. I've made many mistakes along the way. I've tried my best to learn from them, but Effective XML was the book that made everything click for me. The best part is that the book went well beyond just helping me see my errors. I've already applied some of the ideas to new work I've done recently and have been able to head off some of the problems I would have encountered.


Effective XML is by far the best XML book I've ever read, and quite possibly the best tech book I've read all year. I might even have to add it to my favorite tech books list. If you work with XML to any significant degree, I can't recommend this book highly enough.

Elliotte Rusty Harold states in the introduction of Effective XML that the book is neither an introductory book nor an XML tutorial. Rather, it is a distillation of the author's experience using and teaching XML and how to use it effectively. The book does a great job of explaining how to use XML and its related technologies.

The book is divided into four major sections: Syntax, Structure, Semantics, and Implementation. Each of the fifty Items packs a lot of information into a few pages. The Items span topics such as why you should Include an XML Declaration (Item 1), Make Structure Explicit through Markup (Item 11), Program to Standard APIs (Item 31), and Write in Unicode (Item 38). Even the Introduction is valuable because it sets the definitions for XML-related terms used in the rest of the book that the author has found to be used interchangeably or inconsistently.

Item 24, Choose the Right Schema Language for the Job, provides a typical example of the great information contained in Effective XML. This Item discusses the strengths and weaknesses of four schema languages: W3C XML Schema Language, DTDs, RELAX NG, and Schematron. The use of programming languages to handle situations that the schema languages can't handle is also discussed. The Item ends with a set of questions to think about when selecting the schema language to use.

I found the book very readable and like that the information is presented in digestible chunks. Effective XML isn't meant to hype XML but to identify what the actual capabilities of XML and its related technologies are and how best to use them. The book does an outstanding job at this task.

Full disclosure: I received a complimentary copy of the book for review.

This is not a book explaining XML. This is not a book that goes into any depth on XML APIs. It is not a book explaining any one XML format like XSLT, RSS, or XSD.

Instead it is a book on how to work with XML. How to design an XML application to take full advantage of the facilties of XML: schemas, processing instructions, XSL transforms, namespaces. It is all structured to slowly introduce you into the complexities, and deserves to sit up on the bookshelf with Effective C++, Java and Enterprise Java.

If you already know the basics of XML, it is actually quite a good way to learn about some of the more esoteric concepts -from the pragmatic perspective. Too many XML books rant about how wonderful some feature like XML schema's extension stuff is, why XML is the most universal format ever, SOAP and WS-* the best protocol for distributed systems ever, and XQuery everything you need for an XML database.

This book bursts the bubble of hype with rational analysis of what makes sense, and what doesn't. Item 28: Use only what you need, is my favourite: A review of the main XML specs and analysis of what really matters, which comes down to #35, navigate with XPath.

If you are designing an XML schema/system/application, you need this book. If you have to put up with architects telling you about WS-MetadataExchange, WS-Transfer and RDF, you need a copy to roll up and hit them over the head. And, if like me, you are involved in standards bodies that produce XML related things, you need to buy a copy for all the other participants, so that what you produce will actually work.

Remember that XML is a language designed for use by people and machines. The machines have the upper hand. But with this book, and some thinking, you can design XML applications that people can use.