Software Development Books

Database concurrency control and recovery is one of pinnacles of computer science. An amazing collection of models, theoretical results, and implementation techniques enable thousands of users to simultaneously pound on a large database implemented on unreliable disks and networks, with full confidence that their data will be correctly stored. This book tells how this miracle is accomplished.

I teach database systems and also do research on databases, including systems-level refinements to concurrency control and recovery algorithms. This book has been invaluable to me in understanding the three major aspects of concurrency control in databases: the beautiful theory, the carefully constructed algorithms, and the specifics of the practice.

When this book first came out two years ago, I read most of it over a period of an intense week. That was such an enjoyable experience, because the book is very well structured and written in a smooth yet careful style. The authors ensured that all required concepts were in place before introducing a new concept. And the prose just flows, rendering difficult concepts understandable through well-chosen examples.

Since then I have referred to this book often with specific questions that arose in my research. Each time, my question has been answered fully in the book.

Each chapter ends with a section entitled "Lessons Learned" which summarizes the key ideas of the chapter and just as importantly, states the practical application of each concept. Some concepts have not yet been realized in practice; the authors are up front about this and explain why.

Mike Tarrani's review does a good job of explaining the similarities and differences between this book and the other seminal book on transaction processing, by Jim Gray and Andreas Reuter. Both books have their place, and both should be on the shelf (and read by!) all those who want to understand transaction processing at a deep level. And I agree with Jim Gray who noted in his foreword to the Weikum/Vossen book that it is likely to become (indeed, has) the standard reference in this field.

Exceptionally clear writing. Encyclopedic in its coverage of transactions. Anyone dealing with transactions (not just DB developers) would find this a very valuable resource. If you need a book on transactions, this should be your first choice.

Tradicionally, the 'transaction' concept is always discussed at the RDBMS classes in the University. But this book goes FAR BEYOND this wide known implementation; with a solid math foundation (some math required, specially set theory and algorithms ) it shows you there are a lot of 'real-life' transactions that requiere some formal methods for defining their implementation.

This book has no discussion or topic regarding any comercial vendor technologies (specially databases), and I think this is very good. The Page and Object models for transaction processing are clearly explained. There's a very nice discussion concerning RAID technologies.

This is not an 'academic' book in all the sense of the word. It can help IT professionals to make better transactional system desing (databases, workflow,e-business,etc).

I would like some RDBMS vendors will include this kind of theory in their documentation....

Before this book was published my primary reference and personal favorite TP book was "Transaction Processing: Concepts and Techniques" by Jim Gray and Andreas Reuter. At over 1100 pages that book thoroughly covered the basics and drilled down into the nuances of transaction processing in a way unmatched by other books on the topic since it was first published in 1993.

This book changes that by going far beyond transaction processing. It starts with the same fundamentals as the older book, and even covers many of the same topics, such as concurrency control, but it addresses each topic from a much wider perspective. For example, the discussion of concurrency goes far beyond the issues of transaction processing as a middleware component. It extends into application, database and search issues. Another indication that this book is more up-to-date is the material on queue managers. While they are at the opposite end of the spectrum from transaction processing monitors, they are integral to any discussion of transactional information systems. More importantly, both transaction processing monitors and queue managers are used in modern enterprise architectures. Having both topics discussed in great detail is a major point in this book's favor.

Personally I intend to keep my copy of the older "Transaction Processing: Concepts and Techniques" because it does cover some of the subject matter more deeply. However, this book has replaced it as my principal reference and if I had to choose between them this is the one I'd go with.

Before reading this book I read "The Unified Modeling Language User Guide". I can say that "The Unified Modeling Language User Guide" is about the theory and "UML 2 and the Unified Process..." is about practice.

I think that both books are must for UML beginners and reference for the UML professionals.

In "UML 2 and the Unified Process.." authors show UML in action within the Unified Process, a framework for software development. The book describes how to analyze and design a software by giving a real example. Given examples are also complete and available online.

The language of the book is simple (easy to understand) and its contents is organized very well.

This book gave me an insight about the UML and also introduced me to the Unified Process. I would recommend it with 5+ stars to everybody.

UML has grown. A few years ago, when UML was just getting accepted, a book on how to use it would have been much thinner. But the successful broad uptake of UML led to its semantic notation being expanded. What the authors give us here is a thorough exposition of UML 2.0 and how to use it.

As you might expect, there are numerous examples in UML. Which, to many readers, might be more understandable than a mere abstract diagram. But the book is more than just about explaining the UML semantics. It also goes into the Unified Process for running a project, and how this can be documented in UML. By doing so, the authors hope to better enable an understanding of both.

There is also something else, related to the above, but sufficiently different and important to warrant notice. If you write in any object oriented language, it requires certain skills in designing classes and how they interact. Part 4 of the book concerns these issues, which it discusses under the rubric of "Design". A good explanation of the basic concepts. Like inheritance versus aggregation, or inheritance versus interfaces. Or why the lack of multiple inheritance in a language like C# or Java is not necessarily a deficiency.

As a matter of fact I'm not an UML fan nor I particularly favour unified process. Indeed, I'm much more into Agile Development and XP.

The authors do not try to explain why unified process should be better than other processes. They just describe the method: It's up to the reader to decide which parts of the method are good or bad for his job. The reader is not bored with long enthusiastic comments on how he will be a more capable engineer after learning UML and UP. Unified Process is described in an unbiased and precise way: even those who do not favour UP may gather new and interesting ideas to incorporate in their development method.

The approach on UML is even more interesting. The basic ideas is that graphics should be a view, but what matters is text (which *is* something that the UML creators *did* think). Far to many lesser books focus on diagrams and miss to explain the interesting part is their semantics and their descriptions. Indeed, I try not to use UML unless I'm rather sure it's the best way to express a given concept: this book is a helpful reference on how to write correct and practical specifications using UML.

This is a great useful book.

This book gives a good introduction into modern software enigeering and I think that especially the first chapters about basics in object orientation and how the whole process works should be read by every person participating in a software project. I think these chapters are also worth reading for non computer science people.

This book is basically a manual for Unicode 3.0. It is not a light read but well worth the price and then some just for the glyphs from all of the various scripts that Unicode supports.

At 1040 large (8.5 x 11) pages it is the ultimate guide to unicode. With information on scripts and glyphs I had no idea even existed.

However if you are just getting started with Unicode I would recomend you get Unicode a Primer written by Tony Graham from M&T books. If you understand or feel you are starting to understand Unicode then The Unicode Standard Version 3.0 is the best comprehensive reference on the subject out today.

Consider it an overview of the developing UNICODE standard. As such, it will serve the engineer working on software in English and many other European countries rather well. It will be a good _starting_ _point_ for engineers developing software for other languages.

This book is essential for software engineers, at least for the next ten years or so. All programmers should understand characters, and UNICODE is the best we have for now. Even if you don't need it in your personal library, you need it in your company or school library.

The standard is flawed, as all real standards are, but it is a functioning standard, and it should be sufficient for many purposes for the near future.

The book itself is fairly well laid out, contains an introduction to character handling problems and methods for most of the major languages in use in our present world as well as tables of basic images for all code points. Be aware that these are _only_ basic images. For most internationalization purposes, be prepared for more research. (And please share your results.)

**** Finally, UNICODE is _not_ a 16 bit code. ****

(This is well explained in the book.) It just turned out that there really are over 50,000 Han characters. (Mojikyo records more than 90,000.) UNICODE can be encoded in an eight-bit or 16-bit expanding method or a 32-bit non-expanding method. The expanding methods can be _cleanly_ parsed, frontwards, backwards, and from the middle, which is a significant improvement over previous methods.

Some of the material in the book is available at the UNICODE consortium's site, but the book is easier to read anyway. One complaint I have about the included CD is that the music track gets in the way of reading the transform files on my iBook.

This is not just a reference for computer people, but for anyone interested in alphabets, symbols and character sets.

Central to the book, taking up the larger part of it, are the tables of the characters themselves, printed large with annotations and cross-references. If you enjoy the lure of strange symbols and curious writing systems then browsing these will occupy delightful hours.

For the Latin alphabet alone there are pages of accented letters and extended Latin alphabet characters used in particular languages or places or traditions: Pan-Turkic "oi", African clicks and other African sounds, obsolete letters from Old English and Old Norse, an "ou" digraph used only in Huron/Algonquin languages in Quebec, and many others, particularly those used for phonetic/phonemic transcriptions.

The Greek character set includes archaic letters and additional letters used in Coptic.

Character sets carried over from previous editions with additions and corrections are Cyrillic (with many national characters), Armenian, Georgian, Hebrew, Arabic (again many national and dialect characters), the most common Hindu scripts (Devanagari, Bengali, Gurmukhi, Gujarati, Oriya, Tamil, Telugu, Kannada and Malayalam), Tibetan, Thai, Lao, Hangul, Bopomofo, Japanese Katakana and Hiragana, capped by the enormous Han character set containing over 27,000 of the most commonly used ideographs in Chinese/Japanese/Korean writing. Then there are the symbols: mathematical/logical (including lots of arrows), technical, geometrical, and pictographic. You'll find astrological/zodiacal signs, chess pieces, I-Ching trigrams, Roman numerals not commonly known, and much more.

Scripts appearing for the first time this release are Syriac, Ethiopic, Unified Canadian Aboriginal Syllabics, Cherookee, Runes, Ogham, Yi, Mongolian, Sinhala, Thaana, Khmer, Myanmar, complete Braille patterns, and keyboard character sets. And yes, there are public domain/shareware fonts available on the web that support these with their new Unicode values.

There are very good (and not always brief) descriptions of the various scripts and of the special symbol sets. Rounding out the book are some involved, turgid (necessarily so) technical articles on composition, character properties, implementation guidelines, and combining characters, providing rules to use the character properties tables on the CD that accompanies the book. After all, this is the complete official, definitive Unicode standard.

Of course this version, 3.0, is already out-of-date. But updates and corrections are easily available from the official Unicode website where data for 3.1 Beta appears as I write this. My book bulges with interleaved additions and changes. And that's very good. Many standards have died or been superceded because the organizations behind them did not keep up with users' needs or the information was not easily accessible.

Caveats?

The notes on actual uses of the characters could be more extensive, particularly on Latin extended characters. More variants of some glyphs should be shown, as in previous editions, if only in the notations.

Some character names are clumsy or inaccurate (occasionly noted in the book), because of necessity to be compatible with ISO/IEC 10646 and with earlier versions of the Unicode standard. For example, many character names begin with "LEFT" rather than "OPENING" or "RIGHT" rather than "CLOSING" though the same character code is to be used for a mirrored version of the character in right-to-left scripts where "LEFT" and "RIGHT" then become incorrect. And sample this humorous quotation from page 298: "Despite its name, U+0043 SCRIPT CAPITAL LETTER P is neither script nor capital--it is uniquely the Weierstrass elliptic function derived from a calligraphic lowercase p."

Although the Internet and web commerce is still very much an American phenomena, there are many signs that it is about to change. After many years of explosive growth, the curve of new Internet users in the United States is leveling off. Recent articles point to other countries, Brazil in particular, where there could be an explosion of new users. Argentina, India and China also show signs of being poised to enter the only true global market.
To compete in this arena, it is necessary to understand how to display the characters of the "local" language, and for that, you need Unicode. This book is absolutely the best reference on Unicode that currently exists. Often overused, the word definitive is an understatement. Created by the members of the Unicode consortium, it is difficult to conceive of an aspect of Unicode that is not covered in this book.
However, Unicode is more than just characters in spoken languages. With significant sections devoted to mathematical and other commonly used symbols, this is a reference for all who wish to communicate effectively. In every area, there are some references that are essential, and this is one of them.

This book is here to help the beginner in Apache, PHP, Perl and MySQL. If you have always fancy in setting up your own web server but have no idea of how to do it, this book is for you.

The author teaches you step-by-step from installing Apache web server, PHP and Perl to writing applications like database-enabled web applications using Perl, PHP and MySQL. He also touches a small portion of SSI (Server-sise Includes).

This book is indeed very good for beginners. However, please be warned that you may get frustrated by the typos and mistakes found in this book. Refer to the previous post, he mentioned some configuration issues which are helpful. Other than that, this book is definitely worth reading as you may learn a lot especially when you have no idea of what and how to use Apache, PHP, Perl, and MySQL.

For advanced readers, you may want to look into other books :)

I want to congratulate the author for writing such an excellent book for beginners to open-source software like Apache, PHP and mySQL. On windows platform does not bother me as it is the predominant operating system platform and easier to relate to, although I do hope the second version of this book might include a Linux-version.

The CD software includes the latest version of PHP, MySQL, Apache and Perl, although personally I think Perl should be less covered since PHP is much better. Also the section of IIS installation with PHP kind of distract the attention from Apache in the whole book.

Some typo errors in the book's codes, as well as installation errors not mentioned in the book could frustrate non-technical people: e.g. Not able to set up on my Windows XP (Home) for virtual host / Server Side Include / OpenSSL / Preventing Directory listing...also on PHPMyadmin (Chap 8), the book missed out a step to uncomment in PHP.INI the line extension=php_mysql.dll in order to get the nice result of Fig 8.30, otherwise you would contantly get this error "cannot load mysql extension'.

Overall the book is recommended to read through in one session (I spent 3 hours in one single night), then follow by practices in few other sessions on Apache, PHP and MySQL in sequence.

It has been an enriching and enjoyment experience for me. I highly recommend to all new commers in web-database application developers.

Eric Hunley's USING OPEN SOURCE WEB SOFTWARE WITH WINDOWS addresses some common issues with open source documentation, from Linux/UNIX focuses not easily accessible to Widows users to adapting these focuses to Windows environments. Chapters tell exactly how to adapt open source software to Windows environments, using four of the most popular Internet programs as examples. The focus on how to reduce costs in the process is also a welcome one.

While there is an awful lot of software available on the net, this book concentrates on software related to setting up web sites on systems running the Windows operating system. This includes the Apache web server, PHP to provide web/database interconnectivity, MySQL database, and Perl to provide more flexibility to your web sites. The CD-ROM included with the book includes copies of all of this software, so here is really all that you need to put up dynamic web sites.

I gues the question I would have to ask is that if you are using a system for a single application such as being a web server, why wouldn't you go all the way and use a Linux operating system under it, it would be faster, more reliable and less expensive. But if you gotta use Windows, here's all you need.

Probably the most readable introduction to the Z formal method that I have seen. Jacky does a great job of showing the reader why Z might be useful, gently introducing the concepts, and showing how they can be translated into real code. While this book is not a comprehensive Z reference, it is certainly a wonderful introduction that will give the reader most of the tools they might need (and a great background for learning any of Z's more obscure corners).

This book is the first book I've read on Z or formal methods. It's very easy to read and understand, and replete with Z examples. I recommend it to anyone who's interested in learning Z.

The thing I found most helpful about this book is that the author presents Z in comparison to things that we are already (probably) familiar with: data flow diagrams, state charts, etc. He shows the difference between Z and these things, and walks you through a comparison of one system using all 4 different methods.

There are many good books on how to construct, verify, and establish actual program code using Z. I have read bits and pieces of many in an attempt to gain a general understanding of the whole development process and a breadth of approaches taken to it. I cannot say that I have come accross a book even approaching The Way of Z in both clarity and completeness. Dr. Jacky has left nothing out of this text and it reads extremely smoothly (without the sacrifice of complexity). I recommend it to any Formal Methods student, programmer and anyone interested in the formal specification, verification, and implementation process.

I just got this book, having pre-ordered it awhile ago. As a BREW games developer, I am finding Mr. Barbagello's explanation of some of the finer points of BREW very useful. I've already had a few "Doh! So *that's* how that works!" moments, and I would recommend this book to anyone who is interested in coding applications for BREW. BREW has a definite learning curve to it, but this book could make that much easier. You should have a good grounding in C/C++ before diving in, though, so be warned. The book has an extra section on how to construct BMPs in memory for use in BREW, which sounds easy enough, but if you know anything about BREW, isn't. Overall, a wonderful book I wish I'd had when I was learning BREW.

It's amazing that so little has been written on BREW, but with this book the above author is at the forefront of the upcoming tidal wave announcing and providing us an insightful and indepth how to manual on how to develop and publish BREW applications.

This book is a great gift for BREW developers, Out of two books available for the Qualcomm's BREW this one has definitely more advantages, Even it doesn't matter that you are a Game Developer or not this will help you if you want to a become a BREW developer.
Amarjeet Singh
Bangalore India

This book (Wireless game development in c/c++ with brew) was pretty good. It is the best info I can find on the subject. There were only two books that I found about brew the other being Qualcomm Brew platform by Ray Rischpater, but If you are going to become a brew developer it might be in your best interest to drop the 80$ and get both books.

This one was the best out of the two I did get.

Also, even though the book has the words 'game development' in the title, it is a great book for non game dev people. My applications have nothing to do with games.

comman

This book starts off reviewing the basic concepts of OpenVMS and then gets into some real solutions for real problems. Nicely updated for todays VMS programmers.

DCL is the native scripting language of OpenVMS. Like batch files in DOS, or shell scripts in Unix, DCL makes all features of the VMS operating system available to you. This book takes a very useful, complete, and organized approach toward DCL and the VMS operating system. If you're just starting in VMS, or if you want a well indexed sourcebook of powerful VMS DCL services, this is an excellent book for you.

This book is very good for beginners in DCL and also a very good dictonary for already experienced people. This book was one of my most borrowed ones in my bookshelf.

This book is written in a very approachable style that starts off with a very simple software-only character driver and builds up to more complicated hardware combinations. The code fragments are C code of course, but are preceded where necessary by pseudocode to give a better idea of the underlying algorithm. Complete code is given for the drivers, but this book is not really about programming as such. It probably tells you more about hardware than most programmers ever wanted to know, unless they were asked to write a device driver- which this book presumes you are. The book is biased towards IBM PC interfacing (8250 UART, LPT1, etc) but not exclusively. More importantly the principles remain the same and the author always seeks to explain things and make you think about what is happening. Furthermore the book is based on Unix version 3 (SVR3) with particular reference to SCO Unix, with only the last chapter introducing the principles of SVR4. However streams are treated more thoroughly with separate chapters on a loop-back driver and a rewrite of the terminal driver for COM1. After a general explanation, the book is divided into chapters covering individual drivers in increasing levels of complexity. There are character drivers for a test data generator, an A/D converter, a line printer, a more complicated test data generator, a raw disk driver, and a tape driver. Block drivers cover a test data generator, RAM disk, and SCSI disk. There is a terminal driver for COM1 and streams drivers for a loop-back driver and COM1. Finally, there is a chapter on installation and one on Zen and Driver Writing. The installation chapter refers you to your system manual for specific details, but explains how device installation is meant to work. The Zen chapter is general philosophy on when to write a driver and problems in debugging. Of particular note is the assertion that it is easy to write drivers provided that you have "..a mind unbound to conventional hang-ups about determinism, causal theory, logic, and the expectation that any piece of hardware will work the way its designers described." There have been more recent books on writing device drivers for various flavors of Unix, but none is as instructive and detailed as this book. You may need an additional text on device drivers for the particular flavor of Unix you are working with, but this book is still essential.

If nothing else, the thoroughness of the example code makes this book worth the cost. The variety of exampe types (nic, ram-based fs, etc) make it all the better.

What I'm appreciating about this book is the simplicity and the vigor of the writing. It's *really* easy to make this topic sound really complicated. Pajari's approach lays out as few issues at one time as possible, then adds gradually to the mix. The early parts are not taxing, but the pace does pick up.

In teaching the subject, I often find it difficult to slow students down, and get them to confine their questions to one problem domain at a time. Device drivers have to fit into the kernel subsystem and communicate with a device through interrupts; there are LOTS of side questions people can dream up.

This book gave me a few insights into containing the discussions and forestall all that anxiety. Well worth the wait to get the book.

This book is a priceless collection in the shelf of a Device Driver writer. Whether you are writing device drivers or just want to know more about them this is the book to read. The easy-to-understand language and style adopted by the author is also an added benefit to the reader.

This is the best book on XNA.

I like that the book is not focused on beginner topics but rather on intermediary concepts. This book will help you grow once you got the basics i.e. once you are able to create a simple 2D game or setup a basic 3D scene.

The author is very focused and the recipie approach works great.
I surely hope the author will publish other books on XNA.

Thank you so much for giving us this book. I am getting what all i want to implement my game from your book. Great work Riemer. Please make your next book completely on performance issues and terrain to get the best framerate.

In this moment this is the best book in XNA. Thank you Mr. Riemer for your webside and this book.

I have followed Riemer's site pretty much as soon as he started publishing articles on XNA and loved all his on line tutorials as they gave a good base for those of us starting out and also enough for us to be getting on with once we got past those first early stages.

I am pleased to say that the book is no different in this achievement, each Recipe has enough detail and information for you to pickup the techniques.

I am also astounded as to how much is in here, from the basic data storage in XNA, on to cameras, game components, dealing with models and then onto the usage of vertices's, HLSL, the list goes on!

Great site, great book.

I wasn't convinced by the "recipe-based" approach before I ordered this book, but I enjoyed the author's online tutorials so thought I would give it a shot. I ended up buying and reading what is, pure and simple the best XNA book currently on the market.

Each "recipe" is direct and to the point with a minimum of fuss. Some are straightforward and can be skimmed over quickly, while others investigate the deepest corners of XNA and shine a light upon them. I've been writing games professionally for six years and there were recipes in this book that made me stop and say, "wow".

I'm not convinced it would be a great purchase for beginners - the direct and succinct writing style may not provide enough detail for those who aren't used to creating basic games already. However, there are a plethora of other XNA books targeted at beginners - this one says, "so you know a little bit about XNA? Now let me show you the good stuff."

If I had to pick up on anything, it would be that the book could have done with more diagrams. Sometimes the only way to actually see the results of a recipe, instead of just understanding it conceptually, is to copy out (or download) the example code. This is a minor quibble, because the explanations are clear and to the point, and more diagrams might have meant fewer recipes, which would have been a far bigger price to pay.

An even wider audience will be found for Chris Bateman and Richard Boon's 21st Century Game Design, which examines how best to design games and tailor them for specific kinds of audiences. Chapters focus more on the psyche and needs of the player than most programming or game books, discussing both how games can address these desires and how they can appeal to a wider audience outside the hard-core gamer. Any game designer or those seeking to develop and distribute games would do well to examine 21st Century Game Design with its audience-oriented focus.

I suppose it comes as no surprise to anyone to hear that game design has gotten very complex. The power of computers has grown tremendously since the first games like Pong. And with the ability to do more on the computer, and with more competition in the marketplace the need for a higher class of game designer has become clear.

Now game designers have to consider such things as the age, gender, ability, attitude of the player -- many years ago my daughter got hooked on the Roger Rabit game. I told an executive in the Disney game group that they needed some games for young girls. He turned me down with a huff. 'We have Mickey Mouse,' he said. 'Yes,' I told him, 'but you also have Minnie Mouse.' He tuned me out. Now such a manager couldn't afford to ignore such an audience.

This is a book written by professionals on what it will take to suceed in game development in the coming years. These people have 'been there, done that,' pay attention to what they say.

21st Century Game Design's quiet brilliance lies in its logical, sensible treatment of game design in today's market. Things game designers may know on some intuitive level, but often have no conscious access to, no way of articulating, this book illuminates. Chris Bateman's DGD1 audience model allows designers to make more intelligent, informed decisions in the way they design.

Thorough implementation of the principles Bateman describes would help everyone: help publishers understand and support developers, help marketers know who to target, and most importantly of all, help gamers by making games that are made with their playstyles in mind. Not all gamers game alike, so as our industry grows and matures, understanding and identifying the different types of gamers is essential.

Of particular import for growth of our industry is appeal to women and the casual segment, considerations that Bateman shows need not be commensurate with alienating the hardcore segment. You don't need to "water down" a great game to broaden its potential audience; you just need to be aware of your audience and make design choices accordingly.
Bateman shows us that great game design is ultimately subjective; therefore an audience-driven approach to game design is essential to designing games in the 21st century.


For any colleges and universities that have or are developing game design based cirriculum, for all industry professionals: here is an indispensable text.