Software Books

most chapter's are only 10 pages or less long so you can sit down for 5 minutes read a chapter then come back and read another chapter later as it helps to read a whole chapter at once

where as some books are like 40 pages per chapter and ya need to sit down with a fair bit of time just to read the chapter

Ben Forta's Certified Coldfusion 5 Developer Study Guide will not teach ColdFusion, but will be a review guide that provides helpful pointers for examinees. The book's look will be non-intimidating yet thorough, and will be highly readable in small bite-sized chunks. Each subject will be presented in a clear and direct language, with useful and well explained code examples. Sample questions will accompany each subject, as will references to recommended reading, product documentation, Macromedia course work, and existing ColdFusion books. 432 pp. Intermediate-Advanced user level.

I have been developing with CF for about 4 years now but there were several features I had never used. I purchased this book and within a week got the nerve to take the exam. The book came with a 15% off coupon for the exam so it about paid for itself with that. I passed the exam today and achieved Certified Advanced status. In a word, Outstanding!

The book was helpful, the chapter formats are short and to the point giving you only what you need to pass the, which is good. Just don't rely only on this book...here is a secret, there is a program called cf_buster that is a great test prep that when used in conjuction with this book simulate a certified test environment. I passed my test today.

As with any operating system, it is imperative to have a complete understanding of the intricacies of the workings in order to be the best technician possible. Understanding Routers and the IOS is very important to making sure that they work and work all the time.

This book breaks down the IOS to the basic level and is very complete and the author has made sure that you have every tool at your disposal. From routing and bridging overview to the basic router configuration and components.

There are three chapters devoted specifically to the IOS and the remaining chapters cover topics such as, IP, IPX, APPLETALK, DECNET, VINES routing. Also there is coverage for bridging, frame relay, SRB and DLSW making up another eight chapters.

Completing this book is a 65 page appendix with the commend reference. While this book is tailored to any exam, this book will be very useful for most of the CCNA/CCNP exams.

This book was big help with learning syntax. I've worked on Bay Routers for years, this helped me find my way around. It is good source of info not just answers to exam questions.

Of all the books about Cisco routers this is one that you will want to add to your shelf. It does not focus too much on theory, but it focuses much on the nitty-gritty, the hands on knowledge that you need in the industry. I suggest this book for anyone pursuing a certification or who need any extensive knowledge concerning the configuration of Cisco Routers.

This is the only Cisco router book I've seen that does a good job of actually explaining what something is and how to do it. It answered a lot of my questions. Unless your already an expert, this book is a must.

A good book for high level description of the structure of Sybase System 11. When concerning details, there are many places the explanations are confusing. Pretty often two or more contradiction view of points appear in the same page. Considering the lack of good Sybase books, I would like to give this one a favorable recommendation, but don't expect too much.

This books gives an insight into sybase internals and how to get the best out of your server. The material on locking included in this book is one of the best I have seen so far.

I've got more than 30% improvement in my Server , After reading & use the concept which is describe in this book

Of all the Sybase books that I own (10+) this is the one I look at the most. It is theoretical and practical. Only bad thing I can say about the book is the printing and binding. It is almost 4" thick and wouldn't stay open flat on a bet. The paper is unusually thick and the diagrams look like something from the pre-TeX days that your kid put together with a screen print and Paint. Content is superb. It covers topics in depth that are not covered at all in equally priced books. Only two others come close: the Unleashed book (day to day how to) and the Sugiyama & Roy book (heavy on the theory, light on the real world)

This book is a must have. It uses the dragon book (Compilers: principles, techniques and tools by Aho et.al) as a model but goes a great deal further in its use of examples when explaining the theory. Whenever I had a little trouble understanding the dragon book or wished that more examples were used I turned to Holub's book. The book is extremely well organized. If you want the theory its all there and if you want to just look at code its all there too: thousands of lines of it! After explaining everything you actually get to see how lex and yacc are built (from the ground up) and finally a C compiler. BUY IT NOW!!

This book is more accessible than the Dragon book (Compilers: Principles, Techniques, and Tools) but is less complete. This book presents complete source code for parser generators tools and a C compiler. Even if this book is getting a little bit old and it targets a DOS platform, it should not stop you from acquiring this goldmine of very useful information for anyone interested in compilers for a very reasonable price.

Only a few words. Using this book, I designed a few compilers for testing languages, using Portuguese words and commands. It is yet on the development age, but, without this book it would not be abler at all.

I have had this book for 8 years. It clearly describes compiler theories and examples. It is very useful when I develop very fast parser. (The code generated by lex isn't fast enough.) I am not in the compiler writing business. This book is perfect for me.

I absolutely enjoyed reading the book. This is a book that covers some very advanced topics in a way that it seems so easy to comprehend. I liked the way author uses examples and explains not only the technology but the use of the development tools as well. This is just one the best technical books that I have ever read.

After trying numerous .Net books I found that this one was extremely helpful in getting to know the most important parts of the .Net framework. The book covers a lot of ground, since anything can be a 'component'. The discussion is split into front end, middle tier and back end components. So the scope is big. This book assumes you know .Net, and have played with VS.Net, so don't expect an introductory level text. I think the author does a great job of picking out the most important parts of the .Net framework and demonstrating their practical use in short but useful examples.

I have been disappointed at numerous books that spend ages covering the same ground like introduction to .Net and using windows or web controls, leaving meatier issues untouched. In contrast, Faison treads quickly, and clearly, through major topics in .Net such as (not in order): using windows & web controls, user windows & web controls, Crystal reports, database access & data grids, session management in ASP, security, web services, and so on. Many other areas of the framework are covered in passing; for example a handy section on using the web browser control in .Net.

The discussion of UML in the beginning is a bit fast, particularly the terse presentation of numerous design patterns, but the author's use of UML sequence diagrams through the book is excellent.

My main criticism is that the author tries a bit hard at humor with the quotes before each chapter. Otherwise, it's a great book.

This is a comprehensive book on component-based development (with C#). It's ~1000 pages thick and packed with code and developer information that is well referenced. A bit short on component "packaging" frameworks. This book also complements well Groove development(GDK with .NET)...

Highly recommended for serious software developers.
One of the best books I have read.
Part one is almost biblical to software development process.
This is not just for .NET, the same principles are applicable to Java or Windows developments.
I have good understanding on VC++6.0, but facing VS.NET I feel daunted.
My experiences with the Windows system, MFC class lib and VisualStudio are not much useful.
This book helps a lot. .NET is very rich and deep, so you should not expect
realizing .NET with a signle book. Yet this book is a must on your reading list.

The "Search Inside this Book" feature was not available when this review was posted. This book contains the following (excellent) articles:

TABLE OF CONTENTS

I. COMPONENT DEFINITON.
1. Definition of Software Component and its Elements.
George T. Heineman, William T. Councill.
2. The Component Industry Metaphor.
Hedley Apperly.
3. Component Models and Component Services: Concepts and Principles.
Rainer Weinreich, Johannes Sametinger.
4. An Example Specification for Implementing a Temperature Regulator Software Component.
Janet Flynt, Jason Mauldin.

II. THE CASE FOR COMPONENTS.
5. The Business Case for Software Components.
John Williams.
6. COTS Myths and Other Lessons Learned in Component-Based Software Development.
Will Tracz.
7. Roles for Component-Based Development.
Paul Allen.
8. Common High Risk Mistakes in Component-Based Software Engineering.
Wojtek Kozaczynski.
9. CBSE Success Factors: Integrating Architecture, Process, and Organization.
Martin L. Griss.

III. SOFTWARE ENGINEERING PRACTICES.
10. The Practice of Software Engineering.
George T. Heineman.
11. From Subroutines to Subsystems: Component-Based Software Development.
Paul C. Clements.
12. Status of CBSE in Europe.
Barry McGibbon.
13. CBSE in Japan and Asia.
Mikio Aoyama.

IV. THE DESIGN OF SOFTWARE COMPONENT INFRASTRUCTURES.
14. Software Components and the UML.
Kelli Houston, Davyd Norris.
15. Component Infrastructures: Placing Software Components in Context.
Steve Latchem.
16. Business Components.
James Carey, Brent Carlson.
17. Components and Connectors: Catalysis Techniques for Defining Component Infrastructures.
Alan Cameron Wills.
18. An Open Process for Component-Based Development.
Brian Henderson-Sellers.
19. Designing Models of Modularity and Integration.
Kevin J. Sullivan.

V. FROM SOFTWARE COMPONENT INFRASTRUCTURES TO SOFTWARE SYSTEMS.
20. Software Architecture.
Alexander L. Wolf, Judith A. Stafford.
21. Software Architecture Design Principles.
Len Bass.
22. Product-Line Architectures.
Martin L. Griss.

VI. THE MANAGEMENT OF COMPONENT-BASED SOFTWARE SYSTEMS.
23. Measurement and Metrics for Software Components.
Jeffrey Poulin.
24. The Practical Reuse of Software Components.
Don Reifer.
25. Selecting the Right COTS Software: Why Requirements are Important.
Cornelius Ncube, N.A.M. Maiden.
26. Build vs. Buy: A Rebuttal.
George T. Heineman.
27. Software Component Project Management Processes.
William T. Councill.
28. The Trouble with Testing Software Components.
Elaine Weyuker.
29. Configuration Management and Component Libraries.
Hedley Apperly.
30. The Evolution, Maintenance and Management of Component-Based Systems.
Mark Vigder.

VII. COMPONENT TECHNOLOGIES.
31. Overview of the CORBA Component Model.
Douglas C. Schmidt, Nanbor Wang, Carlos O'Ryan.
32. Transactional COM+: Designing Scalable Applications.
Timothy J. Ewald.
33. The Enterprise JavaBeans Component Model.
David Blevins.
34. Bonobo and Free Software Gnome Components.
Michael Meeks.
35. Choosing Between COM+, EJB, and CCM.
Andy Longshaw.
36. Software Agents as Next Generation Software Components.
Martin L. Griss.

VIII. LEGAL AND REGULATORY.
37. CBSE as a Unique Engineering Discipline.
John Speed, William T. Councill, George T. Heineman.
38. The Future of Software Components: Standards and Certification.
Janet Flynt, Manoj Desai.
39. Commercial Law Applicable to Component-Based Software.
Stephen Chow.
40. The Effects of UCITA on Software Component Development and Marketing.
Stephen Chow.

IX. CONCLUSION.
41. Summary.
William T. Councill, George T. Heineman.
42. Future of CBSE.
William T. Councill, George T. Heineman, Jeff Poulin.
Appendix A. Glossary.
References.
About the Authors.

I hope this helps.

This book is an excellent collection of articles describing all of the important issues surrounding the construction of component-based software systems. Each chapter describes a different aspect of the question of how to build a system using reusable components. Although each of these chapters is written by a different author or authors, they have been edited so that they read as a continuous whole. It is interesting that the editors were able to get some of the biggest names in the field to write articles on their specialties. A look at the author biographies show that they include industry practitioners, academics, industrial researchers, and independent consultants. Together they have a very impressive amount of experience and varied expertise. Perhaps my only complaint is that because so many different topics are covered, and each article is rather brief, some of the articles just touch the surface of the issues. But they do provide a balanced picture of these issues which then allow you to go out and do further in-depth reading on salient topics using the included list of references.

Covers the full spectrum of component-based software engineering, from the basics to legal aspects. Contains one of the most authoritative collections of essays and whitepapers on the subject between two covers. I have used this book as a basis for component-based development, and have also used it as the foundation for a SQA initiative because the material also addresses quality. Many of the essays support a software reuse strategy, which is an added bonus. Another use of this outstanding book is as a resource for in-house training in many aspects of software engineering outside of the component-based domain. It's that comprehensive and complete. I recommend using this book with Successful Software Development as the two primary references in mature development organizations.

This 818 page collection of 42 papers and articles is a definitive work on component-based software engineering. Regardless of your area(s) of interest, there is probably a chapter that addresses it. More importantly, each chapter is written by a top expert in their subspecialty.

Instead of giving a chapter-by-chapter description, I am going to cover the chapters that I found useful. To begin, Part II, chapters 1 through 3 gave me a quick primer in software components and highlighted the need to think in a different frame when dealing with component-based development. If you are new to CBSW then the 48 pages devoted to the basics are worthwhile reading.

Part II's five chapters on making a business and technical case for components is outstanding and the authors cover every facet. I found Part III, which covers software engineering practices, particularly useful. The value to me was the status of CBSW engineering on a global scale because I am currently providing consulting services to an India-based company that specializes in components. For this reason I also found Part IV's eight chapters on managing component-based software systems especially valuable.

The real eye-opener [for me], however, was in Part VIII, which devotes four interesting chapters on aspects of legal and regulatory issues as they related to software development as a discipline, and component-based software engineering specifically. In particular, chapter 38 on software component standards and certification was enlightening. I was also enlightened by chapter 39's fascinating discussion on commercial law applicable to component-based software, and the effects of the Uniform Computer Information Transactions Act (UCITA) on component-based software development and marketing.

This is an excellent book that covers the entire landscape of component-based software engineering and, although is a weighty 818 pages, is not difficult to read through. Each chapter is really a paper or article, so each is standalone. If you are dealing with off-shore development in any way, the book is especially valuable, and if you are doing CBSW in-house, the key differences between this approach and other development approaches are highlighted and will give you sufficient information with which to approach CBSW intelligently and effectively.

Gives a lot of practice questions to do. Answers are provided which is an added bonus. The questions are of varying difficulty. Beginners can gain practice by attempting to answer the easier questions first, before going on to tackle the more difficult ones. Those who are more familiar with Microsoft Word can aquire further knowledge in it and brush up their skills by attempting the more advanced questions. Haven't seen many books like this on the market. Definitely worth the buy.

I am generally lazy when it comes to writing reviews but a book like Computer Tutor sure got me there. Bravo! to the author. Indeed a superb bit of work.

Computer Tutor is a very good book. I like it because it has interesting questions. Someone new to MS Word can get to know the application without the boredom. I took the Microsoft Office User Specialist exam a few weeks back. I needed to brush up on 'Tables' and 'Styles' and Computer Tutor helped me tremendously. I also have other books written by the same author and have enjoyed reading them. Her books are very cleverly written. You can really appreciate their content when you start off knowing absolutely nothing about Microsoft Word and end up passing the MOUS exam!

Finally, someone wrote a book for beginners! Someone understood a beginners needs! I am new to Microsoft Word and most of the books available in bookstores say 'for beginners' but certainly do not live upto it. This book truly helps beginners get a thorough understanding of Microsoft Word.You can also use the book as you get more familiar in MS Word, as it has a range of questions addressing all levels of difficulty. You can grow up with Computer Tutor, as it is useful for the beginner and the intermediate. Even the expert can learn a thing or two from it. It is an unusual and charming book.

This book is fantastic! It's like a more "fleshed out" version of Structure and Interpretation of Computer Programs - 2nd Edition (MIT Electrical Engineering and Computer Science). It uses a neat (if somewhat weird) language called Oz, which has a number of interesting features, which are used to demonstrate the concepts of the book. Much like SICP, this book is a real masterpiece, elegantly composed and explained.

Modern programming has become fragmented into a variety of computational models (OO, functional, imperative, etc), and a variety of languages supporting those computational models. Neophyte programmers are typically introduced to just one of these models, and only learn the other, "less natural" models later. With CTM, Van Roy and Haridi take an alternative approach. They teach programming as an integrated discipline, and demonstrate the underlying links between the different computational models. By the time the reader is done with the book they will have a much better understanding of the discipline of programming, and will be well-equipped to decide which model is best suited to the task at hand. Reading CTM is an extremely worthwhile experience for anyone wishing to achieve a deep understanding of the art and science of programming.

CTM has been compared to Abelson and Sussman's "Structure and Interpretation of Computer Programs". They are similar, in the sense that they both provide the reader with a deeper understanding of programming than most programming texts. However, the content of both books is quite different, and it is definitely worth reading both.

Another book that I feel makes a good companion to CTM is Hoare's (sadly hard to come by) "Unifying Theories of Programming". It covers a lot of the same material as CTM, but in a much more theoretical sense. Where CTM is concerned with practical programming, Hoare is concerned with mathematical underpinnings. The two complement each other nicely.

In 1976 Edsger W. Dijkstra elevated programming to an intellectual discipline and taught us how to reason about what we now call "imperative programming". To illustrate his methodology Dijkstra solved challenging problems with unforgetably beautiful, yet simple and powerful example programs that are as relevant today as they were forty years ago. Since then, programming has splintered into paradigms, methodologies and suffers from baroqueness, perpetuation of obsolete conventions and other practices that restrict the full expressive power of programming "as a whole".

In 2004 Van Roy and Seif Haridi have given us a glimpse of what programming can be like without unnecessary restrictions imposed by paradigms and other heavy baggage caused by politics, ideology and historical inertia. Using the remarkably mature implementation of the Mozart system and the conceptually clean, simple, elegant, yet powerful programming language Oz, Van Roy and Haridi show us how dogmatic heavy baggage falls away when we can look at programming as a whole and choose the best programming concepts that the solution of a problem requires. Such a program becomes simpler, more elegant and therefore less error prone than an equivalent solution that is restricted to a specific paradigm.

This book is a real mind-bender that illuminates paths for computer design at both the conceptual and practical levels I'd never travelled down before.

The notion that one language can be so flexible as to accomodate both the syntax and semantics of so many different computational models, or paradigms, took some unlearning of bad programming practice before its power, elegance and potential began to sink in.

It also explodes the myth that "pure" languages -- i.e., pure OO, or pure functional, etc., languages--have some kind of innate advantage over so-called "hybrid" languages. In fact, "hybrid" (or as the authors would prefer to call them, "multi-paradigm") languages come out of this book looking even more powerful than the "pure" ones, insofar as they allow the programmer to use the right model for each task, instead of trying to make OO fit, for instance, in places where it doesn't fit so well.

The idea here is that each computational model represents a completely different way of approaching a domain problem. Used by themselves, each has its niche. For instance, everybody knows OO is good for domain modelling and busines objects. Prolog-type languages are good for applications that need to apply rules over a set of data. Functional languages are great in mathematical applications. And so on. What is new here is that one can program in an environment in which all of these tools are available in a single core semantics that seamlessly weaves these computational models into a complementary whole. Used together judiciously, with an eye toward program correctness, they make things possible that have long been considered very hard -- for instance, constraint programming.

Mozart-Oz, the underlying technology, is a strange language when you first look at it. It's hard at first to get used to concepts like "higher-order programming" or "by need execution" or "lazy execution" if you are the programming grunt in the field of most modern IT shops, forced by bosses to code in your standard fare -- Java, C#, VB, etc. If OO in Java is like the hammer that makes everything look like a nail, in Mozart-Oz you have a language that is like walking into Ace hardware store, a swiss army knife of a language (conceptually speaking) that challenges you to become a highly skill code craftsman, not just a programmer.

But, if only for the personal growth you will experience grappling with the concepts in this book, I recommend it very highly even to "non academic" programmers (like myself) as well as to any advanced student of computer science. It may be painful, you may scratch your head in places where the concepts just seemed to leap over your cranium, but if you are patient, do the exercises (and at least think about what it would take to tackle some of the research projects), you will grow.

Unfortunately, you may find the languages you work on to be rather confining, and maybe even boring, after you get a whiff of what multi-paradigm programming can do. More likely, however, is that you will grasp very clearly how the language you code in today works, and that can only make you a better software engineer. So do it-buy this book!

Collaboratively developed and written by Karen Mitchell, Craig Savage, and Jim Erwin, Contractor's Guide To QuickBooks Pro 2002 is a straightforward, easy-to-follow guide for setting up and using the QuickBooks Pro 2002 accounting software to expedite one's construction business. Meant expressly for contractors who may be lacking in familiarity with computer software programs, the individual chapters address the basics of using QuickBooks Pro 2002, setting preference, using it to track workers' comp costs and other expenses, recording receivables and payables, keeping track of one's customer base and much more. A solid, "user friendly", highly recommended "how to" manual and reference, Contractor's Guide To QuickBooks Pro 2002 is enhanced with a CD-ROM offering reconfigured construction company files to save setup time, and Job Cost Wizard, a program that swiftly and easily converts National Estimator estimates into QuickBooks Pro estimates.

I PURCHASED THIS BOOK WHEN ALL ELSE FAILED. FOR THE LIFE OF ME I COULD NOT FIGURE OUT HOW TO USE QUICKBOOKS FOR MY HUSBANDS CONSTRUCTION BUSINESS. QUICKBOOKS FOR THE CONTRACTOR GIVES YOU THE INFORMATION YOU NEED IN THE TERMS THAT YOU UNDERSTAND.I FOUND THAT THE HELP MENU IN QUICKBOOKS WAS BASED ON A MAIL ORDER COMPANY AND DID NOT GET THE QUESTIONS I NEEDED ANSWERED.I RECIEVED THE BOOK, READ IT COVER TO COVER AND USED IT STEP BY STEP FROM ESTIMATING TO TO PAYING JOB MATERIAL BILLS.
IT WAS SO EASY AND THE BEST PART IS THE BOOKKEEPING IS RIGHT!!
FINALLY!!
I HIGHLY REC0MMEND THIS BOOK TO ANY SELF EMPLOYED CARPENTER OR CONTRACTOR WHO IS HAVING TROUBLE WITH QUICKBOOKS.
ALSO IT COMES WITH A DISK THAT MAKES IT POSSIBLE TO IMPORT ESTIMATES FROM NATIONAL ESTIMATER. THERE IS EVEN A DEMO TO SHOW YOU HOW. GREAT BOOK HANDS DOWN

I am a systems manager, and know nothing about accounting. However I did know that my husband's construction firm was not using QuickBooks Pro properly. Amazon's helpful search engine suggested that I might like Contractor's Guide to Quickbooks Pro 2002. Amazon sure was right. This book quickly and simply explained how to set up a construction company's accounts and helped me turn two years worth of mis-input data into reliable reports. It also helped me develop a 10 page guide for the company's staff to use when entering invoices and payments.

The authors also have telephone support for reason prices although I have not yet needed to use them. They will also convert a Company's Quickbooks accounts into their suggested standard for a pretty reasonable fee.

I would highly recommend this book to small and medium sized construction companies. The book is wonderful, especially for non accounting types.

I consider this book to be the best on the market for contractors who use quickbooks. I recommend this to clients who use Quickbooks and are in the contstruction industry, or any other line of work that uses job costing. It has many illustrations which make it easy for bookkeepers for whom English is a second language.

The attached CD-ROM is a nice addition which can help contractors who are just getting started get their books set up quickly.

I had to buy this book for a class I am taking, and it has proven very helpful and useful.

John Huntington's book is the THE reference tool in our lighting shop for show control. It has everything you need for the different control languages, in clear and concise formats.It is a must on every theatre technician's bookshelf

John Huntington's new book, Control Systems for Live Entertainment, is one of the most useful and informative books available for anyone interested in theatre technology. The book covers such technologies as MIDI, DMX512, MediaLink, MIDI Show Control, and others.

A well dog-eared copy of the first edition has been in my tool kit / computer kit for the last couple of years. I have found it a valuable resource. It has helped me on-site more than once. The second edition is more comprehensive and organized. Kudos to John in publishing a great resource fit for the student and experienced professional.

George Tucker- Show Control Engineer- Scharff Wesiberg NYC