Software Books

Excellent pocket reference. I'm a 3rd year FP resident and have found it helpful in the office and in the hospital. Just wish there was a new version -last one was in 1997.

Mark Graber and staff have done it again. The 3rd edition of the Family Practice handbook is the most complete day to day reference I use. A practical and common sense approach to medicine that includes almost all family medicine topics that can be encountered each day. I even bring this book home each day for review and to assist me on my call nights. I feel this book is especially designed for the busy practioner who needs quick access of the latest medical info. I feel it is reliable and authoritative and I encourage anyone who practices family medicine and is looking for reliable information to assist them in their daily practice to try this book.

This is an evidence-based pocket wonder. Mark Graber, M.D., et. al. do an amazing job of packing the relevant practical facts needed in a daily practice or ER in a small space. The emergency care chapters particularly provide the kind of memory jogging details of care that one needs while on the job.

If you were stranded on a desert island and could only take one family practice book, this should be it. (But wouldn't you take a good novel instead?) It covers the waterfront with details of diagnosis and treatment of all of the common and most of the uncommon disorders without the clutter of the rare. Good for students and residents in my estimation.

Good layman's level overview of the technical problems with critical control via software and a discusssion of how industry and individual experts are trying to deal with the problem

Henry Petroski has written several books that explore his dictum, "Form follows failure." His thesis is that improvements in engineering are made to overcome the failures of previous design. Petroski's books cover advances in civil and mechanical engineering. Ivars Petersen has written a similar book covering some of the notorious failures in software engineering and the efforts by a few leading engineers to define practices and design methods that can prevent such failures from recurring.

Fatal Defect describes dozens of software failures, how they happened, and the efforts to correct them. The defects occur in banking systems, stock exchange mechanisms, aircraft and spacecraft guidance computers, medical equipment, telecommuncations, and scientific computation. Some of these failures are famous; others are little known. Regardless, the descriptions always provide the kind of technical detail that you need to really appreciate the situation. Petersen is a journalist for science news and is clearly a professional when it comes to describing technical issues for the intelligent layman.

Moreover, he tells the stories of people who found the errors, lead the efforts to correct them, or who tried to raise the standards of the industry. Nancy Leveson investigated the Therac-25 defect that lead to several deaths in 1986. This influenced her efforts to design software safety standards. Learning from failures requires knowing about them. But the details of many failures are often kept quiet, being marked proprietary or secret to avoid embarrassment or litigation. Peter Neumann tried to open up the discussion of computer failures with RISKS digest. He started it in 1985 but even today it remains one the best places to learn about the technical details behind dangerous system failures. David Parnas took the lead in criticizing the Star Wars strategic defense initiative. He noted that there would inevitably be defects in the software and that there was no way to conduct a comprehensive system test, short of a nuclear war. He then moved on to overseeing the engineering processes at the Darlington nuclear plant, ensuring that the software was correct, even though this delayed the project completion by three years. Vic Basili was one of the first to conduct controlled experiments with programming teams to determine which development methods actually produced the most reliable software. For example, in 1982, he established that code reviews were far more effective than functional testing, a result that is only beginning to be regularly applied to engineering practice today. These results lead he and Harlan Mills to develop the Cleanroom process which Mills taught at NASA and IBM.

Petersen tells the stories of these and other engineers, describing their background and how their careers lead them on the paths that they ended up. I'd been familiar with the ideas of many of these people, but i found it very interesting to learn of the experiences that had lead them to formulate and articulate these ideas.

The issue of what constitutes effective means for developing reliable software is becoming more than just a practical matter with recent events. Earlier this year the Texas board of professional engineers started licensing software engineers and the Institute for Electrical and Electronics Engineers plans to start certifying software engineers in 2000. Licensing means more than just professionalism and status. It also means acknowledging accepted practice and deviating from it at the risk of malpractice. If the licensing process is done well, it will base itself on the fine, but tentative work done by the people described in this book. If it is done poorly, it may merely enshrine the latest fad in law.

Ivars Peterson has written a well thought-out and interesting book that provides just the right amount of depth to this fascinating subject. Both the layman and the software engineer will find Fatal Defect interesting reading.

This book should be required reading for everybody in the IT industry!

From the subtitle, "Chasing Killer Computer Bugs," you would think that this would be a book about software testing. It isn't. Rather, it's a book about things going wrong with software. The author tells readable stories about some infamous software bugs, at least one of which I've never been able to forget. This is the story of the Therac-25 radiation therapy machine, which caused deaths and injuries due to a software problem. Some of these stories have morals which software professionals would do well to keep in mind--and not just developers, but the people who give them their marching orders. For instance, the Therac-25 story makes clear in a very sobering way how an apparently VERY minor change to a program can have VERY unanticipated consequences. The A320 story makes a convincing case for thinking hard about user interface design.

Other parts of the book talk about why building good software can be so hard, and about some of the people and organizations that work towards developing approaches to issues in software quality and construction. You wouldn't think that these would be particularly interesting subjects, but for the most part the author makes them come alive.

This is not a technical book--don't expect to come away from it with any new debugging techniques. Rather, expect it to give you lots of food for thought.

Great reference book. I think every function and aspect of FW is in here! I have already found out a lot of new things about FW from this book! Lots of great ideas too! There are not many FW 4 Books available, but this one is definitely worth a look!

Great reference book. I think every function and aspect of FW is in here! I have already found out a lot of new things about FW from this book! Lots of great ideas too! There are not many FW 4 Books available, but this one is definitely worth a look!

I think anyone serious about Fireworks needs this Bible as a reference source. The index is excellent for looking up quick answers. Its a bit "design" challenged and if you have version 3 the major portion of the illustrations are the same.

You could learn Fireworks with this book if you are patient or have a lot of time, but its better suited as a reference book. The layout and order of things don't flow like a step by step, beginners book.

Don't get me wrong, this is an excellant book with a wealth of information. If you are looking for inspirational design ideas then this isn't it. There are some more advanced topics such as customizing Fireworks and a chapter on integrating Fireworks with Dreamweaver. Good value for the money. If you want to find info quick, this book fits the bill.

I highly recommend this book! I like the way the author didn't waste my time trying to include little jokes to spice up the text. Every feature was covered in complete detail. I read the book from cover to cover and immediately became a master at using Fireworks 4. Previously, I had been using photoshop to make my web images and effects but since reading this bible book I haven't touched Photoshop. Fireworks is a great program and if you want to learn all of its capabilities then you should own and read the Fireworks 4 Bible.

I didnt buy this book to learn about flash coding, or web development. I bought this book because I am interested in Software rendered graphics. That is, applications that dont utalize OpenGL or Direct 3D for rendering to the screen. I bought this book for the techniques it discusses in "faking" 3d, and also producing real 3d. So far it has done a perfect job in giving me ideas and techniques that I can use in my applications. For anybody interested in producing anything that is real time, and 3d, I would reccomend this book.

This is the best book I have read in years! If you know the basics of ActionScript and you know sine and cosine, this book opens up whole dimensions of possibilities for both games and business applications of Flash.

It is clearly written and reads more smoothly than most programming books. While it does assume a basic literacy with ActionScript, it does not leave you flailing with complex 3D concepts. You may have to pull out your definitions of sine and cosine, but beyond that, it is pretty light lifting.

The genious of the book is that it violates commmon assumptions, and this results in simple, elegant techniques that are also powerful for a wide range of problems. The common assumption is that Flash doesn't do 3D. Don't believe it anymore. If you are willing to use some basic limitations to your application (such as keeping your polygon count down), you can have some smoothly flowing, useful 3D applications with relatively little effort. And unless I'm mistaken, those applications will run equally well on a browser running on a Mac, Windows or Linux.

The solutions are simple and eclectic. The authors have created a variety of 3D engines - each optimized for a given purpose. The engines are simple enough that (in theory) you can take the source and enhance it to your needs. Each technique is backed up by source code that you can download from the publisher's web site. But don't shortchange yourself with only the sample code - the explanations in the text are worth the cost of the paper book.

Here are my favorite techniques:

* ch 8 (P 195) - Drawing API and Math for 3D - here they explain and provide a working polygon 3D engine. The demos work smoothly (at least 20-30 frames per second) on my cheap Dell laptop. The demos include a oragami bird and a rocket ship with at least 10-20 polgons each. It doesn't support bitmapped textures, but it does offer fill color and shading support.

* ch 9 - 3D Slice Engine - this is the more clever, powerful and non-obvious technique of the book. Check out "dad.swf" in the binary samples from the web site to get an idea of the power of this approach - the author has made a 3D talking head of his father from a photograph! The idea here is that if you can view your 3D world as a topographical map, then you can model it with a set of parallel planes, where each plane represents a certain cut through the entire 3D model. This approach, though not immediately intuitive, is extremely powerful in Flash because it plays on the strenghths of Flash. Each plane is represented by two "movieclip" objects, with one embedded in the other. The first one handles scaling, and the second handles rotation, within the scaled clip. The hidden surface problem is finessed because the planes are parallel - so you only reverse the rendering order once every 180 degrees of change in viewer angle. This enables you to handle full bitmap detail of your scenes, and the result is pretty dazzling! The basic rendering engine requires only about 50 lines of ActionScript!

* Ch 6 - Parallax Scrolling - This name is misleading - it really goes beyond a scrolling 2D game model. In the Wyvern's Claw" example, it explores the idea of building a 3D world like a movie set - with a set of strategically placed flat surfaces (like the fronts of buildings in the studio sets). Each surface is a movieclip, and your script manages the proper scaling and shading as the viewer moves through. The demo then shows an animated walk-through of a small town rendering in such a way. This seems very cool for a potential game.

I'm already using the Chapter 9 slice engine for a work-related project - multidimensional data browsing. So for me, the book was not only stimulating to read but valuable!

TOC:

Chapter 1 Introduction to Flash 3D
Chapter 2 Light and Shadow
Chapter 3 Scaling for 3D
Chapter 4 Isometric 3D
Chapter 5 Focus and Depth of Field
Chapter 6 Parallax Scrolling
Chapter 7 Text Effects in 3D Space
Chapter 8 Drawing API and Math for 3D
Chapter 9 3D Slice Engine
Chapter 10 Departure Lounge: Moving beyond Flash 3D

Chapters 1, 2, 3, 4, 6 and 10 don't require a trigonometry
background. One of Chapter 6 topics uses XML though.

The best chapters for me were 1, 2, 3, 4 and 6.

I gave the book 5 stars because it has something for everyone.
Some people use Flash to create digital art while others use it
for practical purposes. This book delivers to both people.
Unfortunately, I belong to the latter kind and some of the topics
aren't for me.

I also think that some chapters are impractical unless you're
really a math geek. For example, I think Chapter 8 - Drawing
API and Math for 3D -- is unnecessary because you can import
Swift 3D files.

Some of the authors also show you Actionscript without really
explaining what it does (I think they assume you do know trig).
I work for a software engineering firm (not as an engineer
though) but I do know that it's bad practice to embed magic
numbers -- literals that don't have apparent meaning -- in
any code. It's better to put them in constants.

One of the authors (the Chapter 4 author I think) said to get
a good book on trigo. I don't think I will because there are
plenty of free trigo tutorials on the web. I agree though that
to get the most out of Flash and this book, learning trigo is a
must.

This has to be about the best book I have ever seen. The 3D cheats in it are amazing -- and you surely wouldn't know you were cheating. There are some incredibly insightful techniques, and some more staple things if you're not quite steady on your feet yet.

I think I am, but this book showed me how much more there was to know!

a great book for any flash student with superb examples . a must for anyone connected to computers..

This is a quite thorough book that picks up where Mohler's intro book leaves off. It's written as if a Flash instructor literally transcribed his class presentations, which is good and bad. Explanations are long, but at times are wordy and dull. It will remind you at times of tedious homework assignments and drills. There is quite a bit of slogging through pages with only two or three long paragraphs with no Flash code. That's not bad, but it's a sign that an editor probably could have tightened up the writing here.

Also, these authors need to lighten up and learn to write! The tone they take is often "academic", with all the snobbiness and overuse of big words and long sentences that comes with that. Often it's clear that one or the other of the two authors has written a particular passage--and there are some awful clunkers there. Better instructors and writers strive for a more human, friendly tone.

Also, there are coding techniques that seem to me not to reflect current or common Flash coding practice, like the frequent use of the eval() function and the set() function (which I've *never* seen other advanced Flash authors use).

One good thing: the two long projects in the book are kind of neat, definately better than in some other big Flash books.

I'm a beginning flash user, and I picked this book up as a follow up to Mohler's first book. Even though it explores advanced scripting, the explanations are clear enough for beginners like myself to understand. I actually understand OOP because of the great dog class example. There are some really great examples on the cd-rom. It's so helpful to have an actual Flash file to play with, so I can see exactly how it works.

I bought this book a couple of weeks ago and I love it. It has tons of examples in the CD. It is a great book to learn complex actionscripting.

A fantastic book. Not one of those that you'll be able to get through over a weekend but is one of those books that you constantly go back to for reference or validation. Some of the techniques take the mystery out of capacity planning and forecasting performance. Excellent.

This is not a book about Oracle Performance tuning. This is a book about Oracle Performance Forecasting. This should be evident after carefully reading the book.

Good books, like good professionals, are rare. This is why I have developed a tendency to choose carefully before buying one and, in the Oracle area in particular, I can smell the author's intellectual honesty and trustworthiness from the first page.

Forecasting Oracle Performance is one of those. I enjoyed the fluid style and closeness of the author. I enjoyed the simplicity and clarity, almost reminding me of Wittgenstein's famous quote ("everything that can be said can be said clearly"). I also enjoyed these short touches of humanism (cf Erlang Krarup's life).
On the forecasting subject, I liked the book construction and the quality of the examples.

Chapter 1 gives a landscape picture of Oracle forecasting and puts the reader in scope and context.
Chapter 2 introduces the reader to the basics of forecasting and the basic concepts over which the book is built: Transactions, response time, arrival time and basic formulas are described here.
Chapter 3 shows the limits of basic forecasting (essential formulas) and the problem of baseline and model selection. It shows how to increase forecasting precision with ErlangC or weighted averages. Most importantly, it shows why it is essential to understand the concepts and implications of the application of a given formula, model or method. The author is very careful in the choice of terms and always clears potential ambiguities. Those who know how difficult it can be to forecast will appreciate it.
Chapter 4 introduces to statistics applied to forecasting.
Chapter 5, on practical queuing theory, is probably the biggest chapter of the book. After a brief introduction to queuing theory, Little's law and Kendall notation, this chapter provides such a diverse set of examples (27!) making the topic very intuitive to non-specialists.
Chapters 6 & 7 describe forecasting methodology and workload characterization. The first describes the steps across a solid performance forecasting methodology, from the initial question to the actual forecast. The second deals with workload characterization: how to get system and Oracle data, how to choose the source and peak. It describes the workload modelling and the risks of data collection.
Chapters 8 and 9 are about models: ratio and linear regression models. They describe their respective foundations, limitations and advantages. Each chapter also contain several examples and case studies to illustrate the subject.
The last chapter deals with scalability models and their relationship with forecasting models.

Overall, I found this book very useful. You will find additional resources at the author's website (there is also a discussion forum on forecasting). The errata page is always up-to-date and some examples have even been extended. Great work!

I've always been a fan of Craig Shallahamer, an author who explains complex concepts in plain English.

This is not a trivial book, but it's an excellent book for performance tuning, a worthy book for the worthy scholar.

Oracle STATSPACK and the automated workload repository have provided a gold mine for the Oracle DBA to forecast future performance, and this is a great "get started" book to the statistical techniques that are required to perform performance forecasting.

This is a great book to do FORECASTING, that is, if you already have a tunning problem you will not find the solution here. If you are in calm times regarding your application speed, this is when you have to do Performance Forecasting, for which this book is excelent. Very practical and just enough technicall to grasp the priciples.

This is a really useful book. It's a must if you need to look deep into the Function Point Analysis and get a clear understanding of what this is all about. As a professional and local instructor in Function Point Analysis I've got a lot of inspiration from this book for my course. I believe that beginners would gain even more from this book, however. It covers all topics from the current IFPUG Function Point Counting Practices Manual (release 4.1). It guides you all the way through the whole process and presents a lot of examples and additional explanations on the way.

Beside the operational guidelines this book also describe the Function Point Analysis in the perspective of related topics as e.g. estimation and benchmarking. Those topics are covered very thoroughly as well and the book provides a good insight in how Function Points can be used as a management tool.

In the last chapters "hot issues" as applying Function Points to GUI applications and OO-system development are discussed. Some very useful guidelines are presented here, indeed. But it's my personal experience that mapping OO components to the Function Point concept might be quite more challenging that the book indicates.

Published in 2001, this is a very detailed book on Function Points that follows the guidelines in the 4.1 version of the International Function Point Users Group (IFPUG) standard. Function Point metrics originated in IBM back in the 1970's and spread slowly out to the rest of the world in the late 70's and early 80's. As with anything originating from IBM, it's a process that's heavy on detail and requires a lot of work to get it right. Over the years, FPA has got more and more technical, to the extent that you really need to get certified in it these days (when I first took an FPA course in the early 80's, it wasn't nearly as comprehensive as it is these days, 20 years on..). The authors of this book between them have published a number of articles on the subject and have more than a few years of experience under their respective belts.

The book kicks off with an overview that provides a useful introduction for those "new" to software estimation, although it's still pretty heavy going and it assumes a process-heavy background. If you've worked for a large organization with a comprehensive PMBOK-like methodology, it'll all make sense. If not, you're going to have a headache by the time you finish the first chapter. . There's some good advice on preparing for IFPUG (International Function Point User Group) certification and the authors emphasize the fact that FP counting should only be performed by certified counters. IMPORTANT ENOUGH TO REITERATE - FP counting should only be performed by certified counters!!!! Keep this in your mind at all times. FPA is "Estimating-Heavy", not estimating-light. It don't come cheap in time or education.

The other reviewers have covered the content in enough detail that it's rather pointless to reiterate - suffice it to say I agree with their comments on the content. So, cutting to the chase, if you're looking at books on Function Point Analysis, you've obviously got a serious interest in estimating, and if so, and if FPA is where you want to go, this book is going to be very useful for you as a reference and as a guide. On the other hand, FPA is, while accurate if applied correctly (the nub of the matter.....), both time and expertise intensive - I can't emphasis the expertise factor enough. You need a sizable project with a budget sufficient to fund the additional overhead to make it worthwhile - for your average development project, this is overkill. If you've got a $50-$100 million plus project within the grasp of our sticky little paws and you can get a certified FPA resource on board, using FPA may very well help you stay within your rather sizable budget. And if your're studying towards your FPA certification, by all means delve into this book - it'll help you no end.

But having been there and done that in my past, don't try this at home kids. This book is a great resource, you'll learn all about FPA from it, but reading the book is a completely different kettle of fish to actually doing it. As another reviewer has pointed out, FPA is accurate IF DONE CORRECTLY. To get accurate estimates, you need certified FP counters, and the data needs to be interpreted correctly. Easier said than done. If you want to use FPA yourself, go study and get yourself certified before you try it for real - otherwise, you may well send your career as an estimator down the tubes.

If you've got to come up with estimates and you've got no real estimating experience, DON'T START HERE. Go look at Steve McConnell's book on "Software Estimation: Demystifying the Black Art" to get yourself started. You could also look at Caper Jones' "Estimating Software Costs" although it's a little dated and not up to date with Agile estimating practices (my bias shows through.....). (Subsequent update - apparantly -the second edition (2007) of "Estimating Software Costs" by Capers Jones addresses Agile methods...).

On the third hand, I do give this book 5 stars for what it is. Well-written, understandable, effective - and it follows IFPUG guidelines. If you're after CFP certification, this book won't lead you astray (although it is a version or 2 out of date) and it will prove a useful study aid. I've got it on my bookshelf at work and although I now use Agile Estimating Practices a la Ken Schwaber (Agile Project Management with Scrum) and Mike Cohn (Agile Estimating and Planning), I do take a look at this one every now and then just to see what the FPA guidelines are. Mind you, every time I look thru this book and think of what I might have been doing, I bless Ken Schwaber for coming up with Scrum (OK, OK, I like smaller projects and I like the Agile approach.....).

This is an authoritative book by two authors who have a published a large number of articles on the subject.

Function point analysis is, in both my experience and opinion, one of the most accurate estimating tools a software engineer has at his or her disposal. I have previously used the constructive cost model (COCOMO) through version 2, Raleigh curves, and hybrids such as Software Estimation Analysis Tool, which computes both COCOMO and function point statistics. Granted, not all of these estimating models are equal - the Raleigh curve approach has a focus on quality and manpower loading that the others lack. But each (and many I have not cited) are estimating tools for software development.

My experience shows function point analysis to be the most accurate - if done correctly. Therein lies the crux of the matter. Function point analysis, in order to yield accurate estimates of effort, needs to be performed by certified counters and the resulting data needs to be properly interpreted. That's where this book comes in.

It starts with an overview that serves as an understandable introduction for someone who is new to software estimation, yet is interesting enough to hold the attention of more experienced professionals. The advice on preparing for IFPUG (International Function Point User Group) certification is a highlight and underscores the fact that FP counting should only be performed by certified counters.

The chapters on software measurement and executive introduction to function points are really extensions of the introduction. I found both the software measurement model in this chapter, and how to establish a world class measurement program interesting and informative.

This segues into three chapters that cover measuring and using function points, and industry benchmarks. Some highlights are the way the authors tie function points to key performance indicators such as productivity, quality, financial and maintenance. I also liked the way that the authors stratify the users of function point data into project managers, IT managers and cross-organizational stakeholders. I was particularly interested in the last group because I am often involved in both service and application delivery projects. The use of function points as a basis for service level metrics and outsourcing is an intriguing idea that I will explore further.

When you arrive at chapter 6 the foundation built in the first five chapters prepare you for a detailed, methodical approach to performing function point analysis. This is straightforward and appears to be completely consistent with IFPUG. All you need to know about function point analysis is, in my opinion, provided in the remainder of the book. The material is augmented by case studies, and also addresses contemporary issues such as applying function point analysis to object-oriented, web, client/server and data warehouse applications. While each of these topics are not given in-depth treatment the fact that they are addressed at all is impressive. The authors end the book with advice on preparing for the certified function point specialist exam, and gives sample exam questions. They also provide sample worksheets in the appendices.

This book merits a solid five stars because it is well written, up-to-date and follows IFPUG recommendations. If you are pursuing CFP certification this book will simplify your life. If you want to learn about an effective software estimating technique this book is a great starting point. To be completely fair, if you are new to software estimation you should also read Estimating Software Costs (Caspers Jones), which gives a complete and unbiased survey of all of the major (and some obscure) software estimating approaches.

Even though dated, this is still the best book on Function Points available in the English language. It complies with the 4.1 version of the International Function Point Users Group (IFPUG) standard, while the current version is 4.2. Nevertheless, the book contains many interesting hints and examples not available in the standard. You may also want to buy the IFPUG Counting Practices Manual - the official reference - directly from the International Function Point Users Group.

This is an excellent textbook all the way around. The text is written in plain English and explains every concept in detail. The examples create real life examples that reinforce the concepts. The chapter problems are written well, easy to understand, and provide a great way for students to practice all of the concepts. For an added bonus, the website that goes with this book provides even more tools for learning such as chapter exercises, working papers, and flashcards.

An all around great textbook!

Book was a little more used than described, but hey for the price it couldn't be beat. To bad my sylabus was wrong and the professor changed the edition. Anyhow, seller was excellent. Fast shipping and I would reccommend.

This text was VERY helpful. The illustrations and examples were enough to explain the topic without havung to read the entire book.. Also the problems given at the end of each section were very good. Some were tough; however, the author starts you out with easy problems and works up to the more difficult ones. This text definitely is a good learning aid.

I used this textbook for my first accounting class and it was by far the best. Examples are all spelled out step by step and the numerous exercies and problems contribute to a higher level of understanding. Buy the workbook offered. It will save you a lot of time normally spent setting up the problem. Much better then some of the higher level books I have used.

I recently purchased the "Fundamentals of Signals and Systems" hardcover book written by Benoit Boulet. This book is one of the more complete textbooks i've read not only for Signals & Systems, but for any subject! It is easy to follow with an abundance of tables, diagrams and examples. The CD that accompanies the book is also very helpful for problem solutions and practice exams.

What i liked most about the book is the price. Very affordable which is more than you can say for other textbooks of its kind.

I am a master student in Aerospace enginnering, and I found the book of Professor Boulet a great reference for all signals and sytems topics I am using in my research. His book is written in a clear and straightforward way that makes it easy to find any explanation related to the basics of signals and systems (all transforms, sampling, state models) and even in some more advanced topics. I really recommend it for any student who likes to have all the signals and system concepts in one book. It's not a grad book, but in my opinion, it's a book to keep on the shelf when studying in grad books that usually skip the basics that we tend to forget.

Hope this helps,

Georges Aoude

Signals and systems is one of the core subjects of almost all engineering schools whether the concentration is in electrical engineering, computer engineering, communications, circuit design, or signal processing. In this college level book the author covers all the classical mathematical concepts, how they work, and how to use them to get the results you want or understand the results you get. It is well organized and if followed through from beginning to end each section builds on the previous knowledge and can be grasped easily. Students who use this book should have had a course in calculus and trigonometry as a prerequisite.

The book jumps right into the subject by starting with elementary continuous-time and discrete-time signals and systems. From there it moves through linear time-invariant systems, differential and difference LTI systems, Fourier series representations and transformations, Laplace transformations, time and frequency analysis, applications to electric circuit analysis, state models, feedback control systems, the z-Transform, sampling systems, communications systems, and system discretization. In addition to the normal chapter layout the book is organized into 70 discrete lectures. Designed as an undergraduate academic text for engineering majors it includes exercises at the end of each chapter and a CD with answers to the questions. As a college textbook or an excellent additional text for engineering students Fundamentals of Signals & Systems is highly recommended.

I am of course biased: I wrote this textbook exactly as I needed it for my courses. But why write a new textbook on signals and systems? There are at least 20 out there covering more or less the same material... In a nutshell: Value to the student and engineer. I had two objectives in preparing this book: (1) clarity to enhance learning (by presenting one concept at a time, providing detailed solutions, using lots of figures and learnware applets, etc.) and (2) low cost to the student. I think (2) has been achieved, and I'll let the readers judge (1)!

I was impressed with the authors for their clear and lucid style, assembling and relating diverse topics in a simplistic view, ranging from computer science to philosophy, to present a brilliant holistic view of GIS technical infrastructure.

This book fills a very important gap in the GIS literature. There are many good introductory book about GIS (try Burrough, for example), but they have been mostly written having a geographer or an earth scientist as their prospective reader. By contrast, Worboys writes for the computer engineer or programmer who wants to understand how a GIS really works inside. The author is a leading researcher on the field, and the book is clearly and concisely written. If you are a computer professional working in the GIS area, you'll find this book invaluable.

I'm not your average GISer. I have a BS in Mathematics and worked for 15 years as a software developer. This book was a required text for the class in Advanced Vector GIS that was part of my MS in GIS. I currently use it as a reference as I work on my PhD in pure GIScience.

This book covers GIS data structures and databases in a way that a Computer Scientist would appreciate. It covers GIS algorithms in a way that an Applied Mathmetician would like. It covers GIS topology in a way that a Pure Mathmetician could learn from. It covers uncertainty in a way that a Statistician would enjoy.

If you are, say a graduate student in mathematics or computer science and want to understand what all the GIS hype is about, you've found a great, concise volume that covers an intense amount of information. If you are a geographer who needs to formalize some language concerning theory and methods for a publication, then this is a good start.

If you are looking for something like "how to delineate a watershed in ArcView 9", skip it and look elsewhere.

Having read many books of the kind I can state with confidence that this one is the best introductory book on the topic. The authors claim that the book is best-suited to people approaching GISs with a computer-science perspective and/or background and this should be taken into consideration by all prospective buyers. However, the book should still be a most valuable resource to readers from other backgrounds, as it remains the most comprehensive in its domain, and is very readable thanks to the lucid writing style of the authors.

Each chapter except the first, which serves as a general introduction, deals with a particular sub-discipline within GIS. Chapter 2 describes the basics of databases.
Chapter 3 clarifies important topological and metric concepts.
Chapter 4 enters the area of field vs. object data models.
Chapter 5 deals with raster and vector structures as well as with computational geometry and geometric algorithms.
Chapter 6 moves even closer to the physical computer level and discusses indexes (access structures) and trees.
Chapter 7 is about architectures (distributed, homogeneous, heterogeneous systems).
Chapter 8 talks about GIS-interfaces.
Until that point, the book has a very logical structure with each chapter being the logical extension of the next.
Chapters 9 and 10 exist only in this second edition and provide some brief excursions into the topics of handling uncertainty and time in GIS respectively. They go into somewhat less detail than the previous chapters, yet are very well written.

Remember that this book is introductory, hence dont expect to learn the intricate details of topics such as databases and computational geometry. The authors manage however, to strike a fine balance between the amount of concepts and methods being presented and the degree of detail to which each of them is analysed. Therefore the book retains its clear introductory character while maintaining a very high informational content. In addition, the authors have done a fantastic job at compiling relevant bibliographies at the end of each chapter where the readers may pursue additional details should they wish to. The graphics and figures are also self-explanatory and do a fine job at complementing the text. Verbosity and typos are scarce if at all existent.

I recommend this book as the most comprehensive overview of, and a very good reference source for, GISs. It will be invaluable not only for newbies but also for mid to hi-level experts who wish to consolidate their knowledge or have a trusted reference. Undoubtedly, an indispensable resource in the library of anyone interested in geographic information systems.